Client Configuration Files
Minimum Required Role: Configurator (also provided by Cluster Administrator, Limited Cluster Administrator , and Full Administrator)
To allow clients to use the HBase, HDFS, Hive, MapReduce, and YARN
services, Cloudera Manager creates zip archives of the configuration files
containing the service properties. The zip archive is referred to as a
client configuration file. Each archive contains the set of
configuration files needed to access the service: for example, the
MapReduce client configuration file contains copies of
core-site.xml, hadoop-env.sh,
hdfs-site.xml, log4j.properties, and
mapred-site.xml.
Client configuration files are generated automatically by Cloudera Manager based on the services and roles you have installed and Cloudera Manager deploys these configurations automatically when you install your cluster, add a service on a host, or add a gateway role on a host. Specifically, for each host that has a service role instance installed, and for each host that is configured as a gateway role for that service, the deploy function downloads the configuration zip file, unzips it into the appropriate configuration directory, and uses the Linux alternatives mechanism to set a given, configurable priority level. If you are installing on a system that happens to have pre-existing alternatives, then it is possible another alternative may have higher priority and will continue to be used. The alternatives priority of the Cloudera Manager client configuration is configurable under the Gateway scope of the Configuration tab for the appropriate service.
You can also manually distribute client configuration files to the clients of a service.
The main
circumstance that may require a redeployment of the client configuration files is when you
have modified a configuration. In this case you will typically see a message instructing you
to redeploy your client configurations. The affected service(s) will also display a 
icon. Click the indicator to display the
Stale Configurations page.
