If you're running on EC2, Cloudera Director makes all this very easy for you. The CM API client bindings has some examples here: https://github.com/cloudera/cm_api/tree/master/python/examples ... View more

Client and Service configurations have distinct safety valve parameters in CM. Find the safety valve for Hive clients and make your change there. Thanks, Darren ... View more

Hi dlo, Thank you for your help; you actually led me in another direction and I determined there were 2 "linked" (no pun intended) issues;  Seems that the /etc/hadoop/conf symlink was pointing at another broken symlink, /etc/alternatives/hadoop-conf, that was pointing to a non-existant directory on the 2 nodes where nodemanager was failing.  I corrected the /etc/alternatives/hadoop-conf symlink from /etc/hadoop/conf.cloudera.mapred (which doesn't exist) to /etc/hadoop/conf.cloudera.yarn.   Then I deployed client configuration yet again and restarted the cluster...  and voile`  Problem solved.  When I checked back through everything, I was able to see that the timestamp updated on the  /etc/hadoop/conf.cloudera.yarn/topology.map & /etc/hadoop/conf.cloudera.yarn/topology.py files which was (at some level) a confirmation that the configs had been successfully re-deployed.   Hope this helps and thank you again for your help. mit Freundlichen Grüßen (with Friendly Greetings),      Jan ... View more

You're right that this is unnecessary. We've fixed this in our code branch slated for a future release. Unfortunately, there's no great workaround right now. You could add gateways, deploy CC, then remove gateways, but that's far from ideal. ... View more