You must disable Kerberos prior to executing this procecure.

Using Ambari Web, browse to Admin > Kerberos > and click Disable Kerberos.

In the Ambari Background Operations dialog, stop all pending commands and jobs.

Stop all services.

Backup the Ambari database.

Stop ambari-server and ambari-agents on all hosts.

ambari-server stop

ambari-agent stop

Create *.json file with host names changes.

Example: host_names_changes.json

{
  "cluster1" : {
      "c6400.ambari.apache.org" : "c6410.ambari.apache.org",
      "c6401.ambari.apache.org" : "c6411.ambari.apache.org",
     ....
  }
}

where cluster1 is cluster name and "c6400.ambari.apache.org" : "c6410.ambari.apache.org"is the host names pair in the format "current_host_name" : "new_host_name".

Execute the following command on the ambari-server host:

ambari-server update-host-names host_names_changes.json

After successful end of this action, please update host names for all nodes, according to changes that you added to *.json file.

If you changed the host name for the node on which the ambari server resides, then you must update that name for every ambari-agent.

In /etc/ambari-agent/conf/ambari-agent.ini, update the "hostname" field to the new host name for node on which the ambari-server resides.

Start ambari-server and ambari-agents on all hosts.

ambari-server start

ambari-agent start

Start all services, using Ambari Web.

For each, browse to Services > <service_name> > Service Actions, choose Start.

	Note
	If you have NameNode HA enabled, after starting the ZooKeeper service, you must: Start all ZooKeeper components. Execute the following command on both NameNode hosts: hdfs zkfc -formatZK -force

If you disabled Kerberos before starting this procedure, you must Enable Kerberos Security by working through either the automated or manual setup documented in the Ambari Security Guide.

	Note
	If you enable Kerberos with the manual option, you must be sure to generate and deploy new keytabs that contain the new host names.