Hi @Tulasi,   Greate to hear the issue got resolved! I will report internally on this to our documentation team to see how we can improve on it.   Thanks, Li ... View more

Hi @Travis,   Thanks for the solution. This is great information. @ylchew93, thank you for confirming the solution. That is helpful.    For your information, I did some further investigation, and found out: 1) Starting Cloudera Manager 6.x, hbase.regionserver.thrift.compact propery is set to true by default; 2) From HUE-2692, it looks like Hue has not supported TCompactProtocol protocol yet.   I will file a internal jira on this and see how we can improve in the future.   Thanks! Li ... View more

Hi @nkp,   What is your Cloudera Manager version?   To follow up with gziglgldrum's post, in case you can not access the article, here are some details copied from there:   To configure the maximum heap size of the SCM process, please do: 1) Edit the CMF_JAVA_OPTS property in the /etc/default/cloudera-scm-server file. 2) Alter last line of the file: export CMF_JAVA_OPTS="-Xmx2G -XX:MaxPermSize=256m ..." 3) To configure more heap memory to Cloudera Manager, please change -Xmx2G to bigger value. For example, -Xmx4G. Note:  -Xmx2G option specifies 2 GB of RAM. 4) Restart Cloudera Manager by running below command: sudo service cloudera-scm-server restart   You may also want to read this documentation to find out what is the recommended heap size for your Cloudera Manager: https://www.cloudera.com/documentation/enterprise/6/release-notes/topics/rg_hardware_requirements.html#sizing_cm_server_reqs   Thanks and hope this helps, Li ... View more

Hi @VenkateshB,   You may want to take a look at the doc here where provides some distcp examples: https://www.cloudera.com/documentation/enterprise/6/latest/topics/cdh_admin_distcp_data_cluster_migrate.html#distcp_and_s3   Thanks and hope it helps, Li ... View more

Hi @Tulasi,   Could you please run below command and send us the output? id yarn   Thanks, Li ... View more

Hi @Tulasi,   The banned.users property is to prevent jobs from being submitted using those user accounts. It should not cause NodeManager not able to start problem.   I suggest you checking these doc links: https://www.cloudera.com/documentation/enterprise/5-15-x/topics/cdh_sg_other_hadoop_security.html#topic_18_3 and https://www.cloudera.com/documentation/enterprise/5-15-x/topics/cdh_sg_yarn_container_exec_errors.html   How many nodes does your cluster have? Have you checked all the permissions?   Thanks, Li ... View more

Hi @Tulasi,    Could you please send us the output of below command on all the NodeManager hosts?   ls -alt /opt/cloudera/parcels/CDH/lib/hadoop-yarn/bin/container-executor   The correct permission should be like this: ---Sr-s--- 1 root yarn 53728 Jan 28 14:03 /opt/cloudera/parcels/CDH/lib/hadoop-yarn/bin/container-executor   If it looks different, you can perform the following steps on all NodeManagers: chmod 6050 /opt/cloudera/parcels/CDH/lib/hadoop-yarn/bin/container-executor chgrp yarn /opt/cloudera/parcels/CDH/lib/hadoop-yarn/bin/container-executor Thanks and hope this helps, Li ... View more

Hi @tuk,    Exactly like @truonala mentioned, you need to first upgrade Cloudera Manager to 6.1.0 before upgrading CDH from 5.16 to 6.1.0. So from the page you mentioned, first select "Current Cloudera Manager Version" to be 6.1.0 and then you will be able to see 6.1.0 as the option under "New CDH Version".   You may want to check out this page on details about supported Upgrade Paths: https://www.cloudera.com/documentation/enterprise/upgrade/topics/ug_upgrade_paths.html#concept_tr5_f23_x2b   Thanks, Li ... View more