ambari-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sumit Mohanty <>
Subject Re: duplicate host cleanup
Date Fri, 18 Dec 2015 14:44:14 GMT

one way is to follow the steps here to make agents use the original hostname - introduced a script to change the host
name but its developed against the latest version to be released. It will give you an idea
as to how to modify the DB to make Ambari use the new hostnames.


From: Brian Jeltema <>
Sent: Friday, December 18, 2015 6:10 AM
Cc: Tommy McNeese; Ben Gunter
Subject: Re: duplicate host cleanup

Going back to the original name is undesirable. What other options do I have?


On Dec 18, 2015, at 8:56 AM, Sumit Mohanty <<>>

Hi Brian,

When the cluster was deployed (i.e. host components got added) the hostname used should be
the same that the agents always need to register with.

Say "<>" is what the host registered earlier and later
it switches to "<>" then Ambari interprets it as:
*<> is unavailable
*<> is a new host that has joined

What you need to do is to make the hosts register with the original name. Afterwards you can
DELETE the host entries with the new name. (curl -u admin:admin -H "X-Requested-By: ambari"
-i -X DELETE http://AMBARI_SERVER_HOST:8080/api/v1/clusters/c1/hosts/n<http://ambari_server_host:8080/api/v1/clusters/c1/hosts/HOSTNAME>

If the above is not doable for some reason, reply back on the thread and there are a few more
options that we can consider.

From: Brian Jeltema <<>>
Sent: Friday, December 18, 2015 5:15 AM
Cc: Tommy McNeese; Ben Gunter
Subject: duplicate host cleanup

I just upgraded to Ambari 2.0 on a cluster and ran into a problem with duplicate host definitions.
Somehow, some of the cluster nodes were registered twice with different FQDNs:<><>

The correct name is the first one, but if I look at that host in the Ambari Host page,
the summary section is showing the second one. It appears this is causing the Ambari server
to fail to detected the heartbeat.

How can I clean this up?


View raw message