You can set custom values for this (or any other advanced property that CM does not yet expose a direct UI field for) via safety valves/advanced configuration snippet areas. Read more at http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_mc_config_snippet.html For your goal specifically, target the CM -> YARN -> Configuration -> "NodeManager Advanced Configuration Snippet for yarn-site.xml" field, and drop in the override using a <property>…</property> XML syntax.
... View more
Oops I hit "me to" accidently. Given you actually restarted from the command line, it could be there is a mix of installed CDH deployment types. CDH has 2 modes of deployment, Parcel and Package. If parces are deployed but packages were present first and not removed, the package based installation can start first on system reboot, preventing the parcel based service from starting. Verify if parcels are being used in the CM UI, and if so then check if you have residual packages present that are starting as a service. rpm -qa | grep cdh rpm -qa | grep hue rpm -qa | grep hadoop If they do have a mix of pacakages and parcels, the CM 4 installation guide covers the proper removal of the pacages (rpm or debian). CDH Hue integration on 4.3 is minimal as well. At some point they will want to evaluate catching up with the current release distribution of CDH either on the 4.x or 5.x releases.
... View more