Hi Doron, All configuration properties are in the CM REST API. See the tutorials about using our rest API here: http://cloudera.github.io/cm_api/ These include tutorials about how to read and set config, such as: http://cloudera.github.io/cm_api/docs/python-client/#configuring-services-and-roles Using the rest endpoint for configs directly is documented on the page you linked. There's a different endpoint for each concept (host, service, role config group, role, etc). The one you'd want for Oozie Server role config group is: http://cloudera.github.io/cm_api/apidocs/v10/path__clusters_-clusterName-_services_-serviceName-_roleConfigGroups_-roleConfigGroupName-_config.html Theses configs have the keys oozie_config_safety_valve, oozie_executor_extension_classes, and oozie_workflow_extension_schemas. The most reliable way to identify config keys is to query your live CM via the API, using the option ?view=FULL, as described in the first link above. Documentation for config values is also available here (assuming CDH5.4, you can click other links for other versions): http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_props_cdh540_oozie.html Thanks, Darren ... 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

Hi Doron, You can add the "-c" argument to the file in /etc/init.d if you like. You'll need to re-apply your fix when you upgrade CM. Crashing isn't very common, so we don't plan to add this option by default to our script. You can also consider moving to an independently managed postgresql database (or mysql or oracle), where you will have more control over these kinds of settings. The "embedded" postgresql db from cloudera-scm-server-db is not recommended for production. Thanks, Darren ... View more

It looks like you're starting a process in the background. Cloudera Manager expects that the shell script used to start the role will "exec" the real process. Cloudera manager only tracks the process that it spawns. If you fork a process and then exit your shell script, it will appear as if the process CM just spawned has died unexpectedly, which causes CM to try and start it again. ... View more

Create an initialization command and reference it in your SDL in serviceInit (see https://github.com/cloudera/cm_ext/wiki/Service-Descriptor-Language-Reference#serviceinit). Move all of your one-time initialization logic to that command. ... View more

There are licensing issues with the postgresql library that Hue uses, so we have not been able to incorporate a seamless integration into Cloudera Manager. We'd like to improve this experience in a future release, but I can't promise anything. ... View more

CM does not run the balancer automatically. It must be run manually, or you can set up a cron job to do it. As for how exactly the balancer works, you can ask on the CDH forums for better expertise, or check documentation. Thanks, Darren ... View more