Skip to main content
Cl0ck
Cl0ck
Silver ⭐️⭐️⭐️
December 28, 2019
Solved

Adopting new hostname changes in Cloudera Manager

Aloha. After a recent server migration, all of the hostnames on our cluster got a slight modification. After getting the Cloudera Manager Server to connect to it's required database correctly, it still wants to connect to the old hostnames for everything else in the cluster. Everything is already configured for them to work together, so it should be as simple as updating the URL to connect to the hostname (rather than reinstalling cloudera-scm-agent, etc). Is there a way to do this from within Cloudera Manager?

How?

Shelton
SheltonAnswer
Gold ⭐️⭐️⭐️
December 28, 2019

@Cl0ck 

 

That is possible please follow this cloudera documentation  please have a look and see if it suits your situation.

Keep me posted.

View in thread

2 replies

Shelton
SheltonAnswer
Gold ⭐️⭐️⭐️
December 28, 2019

@Cl0ck 

 

That is possible please follow this cloudera documentation  please have a look and see if it suits your situation.

Keep me posted.

Translate
    EricL
    Platinum ⭐️⭐️
    EricL
    Platinum ⭐️⭐️
    December 30, 2019

    @Cl0ck

    Each host's name is stored in CM's backend database with an UUID attached, please refer to table HOSTS. Example as below:

     

    HOST_ID: 12
    OPTIMISTIC_LOCK_VERSION: 148
    HOST_IDENTIFIER: bfaf4b71-01e2-4157-b46f-d1c13566b69a
    NAME: host-xxx-xxx.xxx
    IP_ADDRESS: xx.xx.xx.xx
    RACK_ID: /default
    STATUS: NA
    CONFIG_CONTAINER_ID: 1
    MAINTENANCE_COUNT: 0
    DECOMMISSION_COUNT: 0
    CLUSTER_ID: 1
    NUM_CORES: 1
    TOTAL_PHYS_MEM_BYTES: 1929342976
    PUBLIC_NAME: NULL
    PUBLIC_IP_ADDRESS: NULL
    CLOUD_PROVIDER: NULL

     


    Where HOST_IDENTIFIER is the UUID, and is stored under /var/lib/cloudera-scm-agent/uuid on each host. Maybe you can try to update the table here for NAME field and see if that can help?

    Cheers
    Eric

    Translate
    Terms & ConditionsAccessibility statement