Configuring Cloudera Manager Agents
Minimum Required Role: Full Administrator. This feature is not available when using Cloudera Manager to manage Data Hub clusters.
Cloudera Manager Agents can be configured globally using properties you set in the Cloudera Manager Admin Console and by setting properties in 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:
- Select .
- Under the Performance category, set the following option:
Property Description Send Agent Heartbeat Every The interval in seconds between each heartbeat that is sent from Cloudera Manager Agents to the Cloudera Manager Server. Default: 15 sec.
- Under the Monitoring 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. Default: 5.
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. Default: 10.
- Click Save Changes.
Configuring the Host Parcel Directory
- Click Hosts in the top navigation bar.
- Click the Configuration tab.
- Select .
- Configure the value of the Parcel Directory property. The
setting of the
parcel_dir
property in the Cloudera Manager Agent configuration file overrides this setting (see below). - Enter a Reason for change, and then click Save Changes to commit the changes.
- Restart the Cloudera Manager Agent on all hosts.
Agent Configuration File
/etc/cloudera-scm-agent/config.ini
file. You must
update the configuration on each host. After changing a property,
restart the Agent:sudo systemctl restart cloudera-scm-agent
Section | Property | Description |
---|---|---|
[General] |
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 Cloudera Manager Server Ports and Ports used by Cloudera Manager. The Cloudera Manager Agent
configures its hostname automatically. You can also manually
specify the hostname the Cloudera Manager Agent uses by
updating the To have a CNAME used
throughout instead of the regular hostname, an Agent can be
configured to use
|
lib_dir |
Directory to store Cloudera Manager Agent state that
persists across instances of the agent process and system
reboots. The Agent UUID is stored here. Default:
|
|
local_filesystem_whitelist |
The list of local filesystems that should always be monitored. Default: |
|
log_file |
The path to the Agent log file. If the Agent is being
started using 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).Default:
|
|
max_collection_wait_seconds |
Maximum time to wait for all metric collectors to finish collecting data. Default: 10 sec. |
|
metrics_url_timeout_seconds |
Maximum time to wait when connecting to a local role's web server to fetch
metrics. Default: 30 sec. |
|
parcel_dir |
Directory to store unpacked parcels. Default:
This
property overrides the setting in Cloudera Manager. To use
the recommended procedure, you must make sure that this
property is commented out in each host
|
|
supervisord_port |
The supervisord port. A change takes effect the next time supervisord is
restarted (not when the Agent is restarted). Default: 19001. |
|
task_metrics_timeout_seconds |
Maximum time to wait when connecting to a local TaskTracker to fetch task
attempt data. Default: 5 sec. |
|
[Security] |
use_tls,verify_cert_file, client_key_file, client_keypw_file,
client_cert_file |
Security-related configuration. |
[Cloudera] |
mgmt_home |
Directory to store Cloudera Management Service files. Default: |
[JDBC] |
cloudera_mysql_connector_jar, cloudera_oracle_connector_jar,
cloudera_postgresql_jdbc_jar |
Location of JDBC drivers. Default:
|