https://community.cloudera.com/t5/Support-Questions/Re-iP-Cloudera-Manager-and-cluster-nodes/m-p/293857#M216915 <P>Hi&nbsp;<a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/76730">@ClouderaAdmin</a>&nbsp;,</P> <P>&nbsp;</P> <P>Thanks for reaching out to Cloudera community. You should stop the cluster for doing the IP changes. See below for some recommendations which may help you:</P> <P>============</P> <P><SPAN>Below document makes the following assumptions:</SPAN></P> <UL> <LI>Hostnames remain unchanged</LI> <LI>Nodes are not added or removed from the cluster</LI> <LI>OS or other software remain the same</LI> <LI>The entire cluster is shut down while the change is performed</LI> </UL> <P><BR /><SPAN>The process should be the same for a secure cluster, as long as name resolution works fine.</SPAN><BR /><SPAN>Changes to be made across the cluster:</SPAN></P> <OL> <LI>Alter all hard-coded IP addresses.</LI> <LI>If<SPAN>&nbsp;/etc/hosts</SPAN><SPAN>&nbsp;</SPAN>is used for name lookups, ensure that all hosts in the cluster are updated.</LI> <LI>If DNS is used for name lookups, allow for&nbsp; TTL expiry so that the new IP addresses are returned to queries.</LI> </OL> <H3 id="toc-hId--1360250753">&nbsp;<STRONG>Zookeeper:</STRONG></H3> <UL> <LI>Nothing specific to worry about if host name lookups are working correctly and quorum membership only has hostnames</LI> </UL> <H3 id="toc-hId--472747072"><STRONG>HDFS:</STRONG></H3> <UL> <LI>Replica availability will be unaffected as the DNs will report in the new IP address when sending heartbeats</LI> <LI>Blockpool name might contain the older IP address but it's just a label and can be left alone</LI> <LI>Exclude and allow host lists should be updated, refer to<SPAN>&nbsp;</SPAN><SPAN>dfs.hosts</SPAN><SPAN>&nbsp;</SPAN>and<SPAN>&nbsp;</SPAN><SPAN>dfs.hosts.exclude</SPAN><SPAN>&nbsp;</SPAN>for file locations</LI> <LI>If racks are configured, update the topology.data file</LI> </UL> <H3 id="toc-hId-1302260290"><STRONG>Cloudera Manager:</STRONG></H3> <UL> <LI>Host to role mapping will remain valid.</LI> <LI>The agent will send in the node's new IP address in the heartbeat.</LI> <LI>Ensure that<SPAN>&nbsp;</SPAN><SPAN>/etc/cloudera-scm-agent/config.ini</SPAN><SPAN>&nbsp;</SPAN>on each node contains the correct hostname of Cloudera Manager node (preferred to a hard coded IP address).</LI> </UL> <DIV id=":2qf" class="a3s"><BR /><STRONG>Note</STRONG>: All other services not mentioned above should continue functioning as is.</DIV> <DIV class="a3s">&nbsp;</DIV> <DIV class="a3s">Hope this helps.</DIV> <DIV class="a3s">Li</DIV> Mon, 13 Apr 2020 20:58:42 GMT lwang 2020-04-13T20:58:42Z