@Stephbat  Please can you check those 2 values dfs.datanode.max.locked.memory and ulimit   The dfs.datanode.max.locked.memory determines the maximum amount of memory a DataNode will use for caching. The "locked-in-memory size" corresponds to ulimit (ulimit -l) of the DataNode user that needs to be increased to match this parameter. The current dfs.datanode.max.locked.memory is 2 GB and while the RLIMIT_MEMLOCK is 16 MB If you get the error “Cannot start datanode because the configured max locked memory size… is more than the datanode’s available RLIMIT_MEMLOCK ulimit,” that means that the operating system is imposing a lower limit on the amount of memory that you can lock than what you have configured. To fix this, you must adjust the ulimit -l value that the DataNode runs with.   Usually, this value is configured in /etc/security/limits.conf. However, it will vary depending on what operating system and distribution you are using please adjust the values accordingly remember that you will need space in memory for other things as well, such as the DataNode and application JVM heaps and the operating system page cache.   Once adjust the datanode should start as a charm 🙂  Hope that helps  ... View more

@focal_fossa  Can you share how method you used to extend you VM disk? Whats the VM disk file extension vmdk or vdi? Note virtualbox does not allow resizing on vmdk images.   Does you disk show Dynamically allocated storage as shown below?   Please revert  ... View more

@focal_fossa  AFAIK  these sandboxes dynamically allocated storage.  You can try that by  generate and load data for TPC-DS General usage is    tpcds-setup.sh scale_factor [directory]   For example below will generate  200 GB of TPC-DS data in /user/data [HDFS]   ./tpcds-setup.sh 200 /user/data     This should prove that the disk allocation is dynamic  see below links   https://github.com/hortonworks/hive-testbench/blob/hive14/tpch-build.sh and https://github.com/hortonworks/hive-testbench/blob/hive14/tpch-setup.sh to build   Hope that helps     ... View more

@tanishq1197    The Password should be the scm password Enter SCM password: The default is SCM that should progress successfully     ... View more

@tanishq1197    I think I did a typo error  previously there was an extra scm the below should run successfully  sudo /opt/cloudera/cm/schema/scm_prepare_database.sh postgresql scm scm   ... View more

@tanishq1197    Please can you copy and paste here exactly the command you run? ... View more

@Fawze  In a Hadoop distribution ACLs are disabled by default. When ACLs are disabled, the NameNode rejects all attempts to set an ACL you will need to enable that manually in CM/Ambari.   Enabling HDFS ACLs Using Cloudera Manager Go to the Cloudera Manager Admin Console and navigate to the HDFS service Click the Configuration tab. Select Scope > Service_name (Service-Wide) Select Category > Security Locate the Enable Access Control Lists property and select its checkbox to enable HDFS ACLs. [Enter a Reason for change, and then] Click Save Changes to commit the changes. The above sequence sets the dfs.namenode.acls.enabled property to true in the NameNode's hdfs-site.xml. This is a cluster-wide operation so only after doing the above you can run the setfacl or getfacl commands against an HDFS file etc <property> <name>dfs.namenode.acls.enabled</name> <value>true</value> </property> The hdfs-site.xml is distributed by CM, when you make a change you are usually warned that there is a stale configuration and you are asked to restart the service this triggers the distribution of the new hdfs-site.xml to all nodes in the cluster and that's precisely the reason to use CM rather than manually editing. Happy hadooping ... View more

@tanishq1197  I think your syntax is wrong  because you have initiated a connection using the below snippet # sudo -u postgres psql  The correct syntax is  without need of prior log on $ sudo /opt/cloudera/cm/schema/scm_prepare_database.sh [options] <databaseType> <databaseName> <databaseUser> <password> Substituting the correct value s the below should run successfully with the default user/password scm/scm $ sudo /opt/cloudera/cm/schema/scm_prepare_database.sh postgresql scm scm scm Assuming you intend to use the derby databases postgres please see Setting up the Cloudera Manager Database Hope that helps ... View more