Deploying the HA NameNode Cluster after installing all the required packages

Enter all host IP’s along with port in etc/zookeeper/cong/zoo.cfg on each quorum node to run
zookeeper in replicated mode rather that standalone.
Example:
server.1=172.31.47.65:2888:3888
server.2=172.31.43.129:2888:3888
server.3=172.31.38.221:2888:3888

Run the command below on every node to stop the services

for x in `cd /etc/init.d ; ls hadoop-*` ; do sudo service $x stop ; done
sudo service zookeeper-server stop

Starting Journal Node on every node.

sudo service hadoop-hdfs-journalnode start

Starting primary Namenode NN1

sudo service hadoop-hdfs-namenode start

Starting Standby Namenode NN2

sudo -u hdfs hdfs namenode -bootstrapStandby
sudo service hadoop-hdfs-namenode start

Starting Zookeeper failover controller

sudo service hadoop-hdfs-zkfc start
Zookeeper didn’t start
First we need to start zookeeper server on each node
sudo service zookeeper-server start
sudo service hadoop-hdfs-zkfc start (on each namenode)

Start Job and task Tracker

sudo service hadoop-0.20-mapreduce-jobtracker start
sudo service hadoop-0.20-mapreduce-tasktracker start

Verifying Active and Standby NameNode

[centos@ip-172-31-43-129 init.d]$ sudo -u hdfs hdfs haadmin -getServiceState
nn1
active
[centos@ip-172-31-43-129 init.d]$ sudo -u hdfs hdfs haadmin -getServiceState
nn2
standby

Stopping NN1 (Active NN) to verify Failover Control

sudo service hadoop-hdfs-namenode stop on NN1

Verify that NN2 becomes active

[centos@ip-172-31-43-129 init.d]$ sudo -u hdfs hdfs haadmin -getServiceState nn2
active
Restart name node on NN1. NN1 should be standby after restarting
sudo service hadoop-hdfs-namenode start
[centos@ip-172-31-43-129 init.d]$ sudo -u hdfs hdfs haadmin -getServiceState nn1
standby
[centos@ip-172-31-43-129 init.d]$ sudo -u hdfs hdfs haadmin -getServiceState nn2
active