Configuring Cloudera Manager Agents
Cloudera Manager Agents can be configured globally using properties you set in the Cloudera Manager Admin Console and by setting properties in individual Agent configuration files.
Configuring Agent Heartbeat and Health Status Options
You can configure the Cloudera Manager Agent heartbeat interval and timeouts to trigger changes in Agent health as follows:
- From the Administration tab, select Settings.
- Under the Performance category, set the following option:
Property Description Send Agent Heartbeat Every The interval between each heartbeat that is sent from Cloudera Manager Agents to the Cloudera Manager Server.
- Under the Threshold category, set the following options:
Property Description Set health status to Concerning if the Agent heartbeats fail The number of missed consecutive heartbeats after which a Concerning health status is assigned to that Agent. Set health status to Bad if the Agent heartbeats fail The number of missed consecutive heartbeats after which a Bad health status is assigned to that Agent.
- Click Save Changes.
Agent Configuration File
|server_host, server_port, listening_port, listening_hostname, listening_ip||Hostname and ports of the Cloudera Manager Server and Agent and IP address of the Agent. Also see Configuring the Ports for the Admin Console and Agents and Ports Used by Cloudera Manager.
The Cloudera Manager Agent configures its hostname automatically. However, if your cluster machines are multi-homed (that is, they have more than one hostname), and you want to specify which hostname the Cloudera Manager Agent uses, you can update the listening_hostname property in the /etc/cloudera-scm-agent/config.ini configuration file on the cluster machines. If you want to specify which IP address the Cloudera Manager Agent uses, you can update the listening_ip property in the same file.
To have a CNAME used throughout instead of the regular hostname, an Agent can be configured to use listening_hostname=CNAME. In this case, the CNAME should resolve to the same IP address as the IP address of the hostname on that machine. Users doing this will find that the host inspector will report problems, but the CNAME will be used in all configurations where that's appropriate. This practice is particularly useful for users who would like clients to use namenode.mycluster.company.com instead of machine1234.mycluster.company.com. In this case, namenode.mycluster would be a CNAME for machine1234.mycluster, and the generated client configurations (and internal configurations as well) would use the CNAME.
|log_file||The path to the Agent log file. If the Agent is being started via the init.d script, /var/log/cloudera-scm-agent/cloudera-scm-agent.out will also have a small amount of output (from before logging is initialized).
|lib_dir||Directory to store Cloudera Manager Agent state that persists across instances of the agent process and system reboots. The agent's UUID is stored here.
|parcel_dir||Directory to store unpacked parcels. See Parcel Locations.|
|max_collection_wait_seconds||Maximum time to wait for all metric collectors to finish collecting data.|
|metrics_url_timeout_seconds||Maximum time to wait when connecting to a local role's web server to fetch metrics.|
|task_metrics_timeout_seconds||Maximum time to wait when connecting to a local TaskTracker to fetch task attempt data.|
|use_tls,verify_cert_file, client_key_file, client_keypw_file, client_cert_file||Security-related configuration. See|
|mgmt_home||Directory to store Cloudera Management Services files.
|cloudera_mysql_connector_jar, cloudera_oracle_connector_jar, cloudera_postgresql_jdbc_jar||Location of JDBC drivers. See Installing and Configuring Databases.|