How to Update /etc/cloudera-scm-agent/config.ini On Cloudera Manager Managed Edge Nodes During Node 3 Migration
(Doc ID 2526029.1)
Last updated on NOVEMBER 08, 2019
Applies to:Big Data Appliance Integrated Software - Version 4.11.0 and later
By default the Cloudera Manager(CM) server runs on Node 3.
Therefore during a Node 3 migration references to the CM server on Node 3 in the Cloudera Manager agent configuration file, /etc/cloudera-scm-agent/config.ini, need to be updated to reflect the new host. The file, /etc/cloudera-scm-agent/config.ini, contains a "server_host" parameter to hold the CM server value. By default it looks like:
During a Mammoth Node 3 migration, the "server_host" parameter in the CM agent configuration file are updated for all BDA hosts in the cluster.
However, Mammoth migration does not update non-BDA cluster nodes. Therefore if the cluster contains Cloudera Manager managed edge nodes Mammoth will not update them. The result is that the config.ini file on those nodes will not have the "server_host" parameter updated to reflect the correct CM server host.
If the "server_host" parameter on CM managed edge nodes is not updated during Node 3 migration, edge nodes can not heartbeat into the cluster and the cluster will not be fully healthy.
To avoid this problem, between the Node 3 migration Step 4, InstallHadoop, and Step 5, StartHadoopServices, the /etc/cloudera-scm-agent/config.ini file on each CM managed edge nodes needs to be updated so the "server_host" parameter contains the correct CM server host.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document