In an enterprise installation, data centers move frequently, so IP changes are also frequent. Assuming such a scenario, this tip describes how to resolve the challenge that BigInsights was installed in a distributed environment using HOSTNAME and now the IPs of these clusters have changed.

If only the IP of NameNode change, configure the data nodes according to these instructions:

1. Stop BigInsights from $BIGINSIGHTS_HOME/bin by entering: ./stop-all.sh

2. Modify the /etc/hosts file to reflect the new IP on all the nodes in the cluster, including master node.

 

In the following example the master node IP is changed from 9.30.91.145 to 9.30.91.199, which has the hostname bvs256xr.xxx.xxx.com

 

/etc/hosts file before:

 

9.30.91.145 bvs256xr.xxx.xxx.com bdvs256xr bigdata1.xxx.xxx.com bigdata1
9.30.90.146 bvs257.xxx.xxx.com bdvs257 bigdata2.xxx.xxx.com bigdata2
9.30.90.147 bvs258.xxx.xxx.com bdvs258 bigdata3.xxx.xxx.com bigdata3
9.30.90.148 bvs259.xxx.xxx.com bdvs259 bigdata4.xxx.xxx.com bigdata4

 

/etc/hosts file after:

 

9.30.91.199 bvs256xr.xxx.xxx.com bdvs256xr bigdata1.xxx.xxx.com bigdata1
9.30.90.146 bvs257.xxx.xxx.com bdvs257 bigdata2.xxx.xxx.com bigdata2
9.30.90.147 bvs258.xxx.xxx.com bdvs258 bigdata3.xxx.xxx.com bigdata3
9.30.90.148 bvs259.xxx.xxx.com bdvs259 bigdata4.xxx.xxx.com bigdata4

 

3. Start BigInsights from $BIGINSIGHTS_HOME/bin by entering: ./start-all.sh

Join The Discussion

Your email address will not be published. Required fields are marked *