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:
node1.mycompany.com <http://node1.mycompany.com/>
node1.foo.mycompany.com <http://node1.foo.mycompany.com/>
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?
Brian
