HDFS的NameNode的NameNode的HA配置
一,zookeeper的安裝(略)。
啓動Zookeeper。
二,Hadoop配置文件修改。
修改core-site.xml
<configuration> <property> <name>fs.defaultFS</name> <value>hdfs://myCluster</value> <description>注意:myhadoop爲集羣的邏輯名,最好與hdfs-site.xml中的dfs.nameservices配置一致!否則在使用hdfs命令的時候,後面跟的路徑就要指定全路徑.如果不一致,那麼執行hdfs dfs -ls /就會報錯(java.net.UnknownHostException: ××××)。但可以通過這樣的命令來執行:hdfs
dfs -ls hdfs://myCluster </description> </property> <property> <name>ha.zookeeper.quorum</name> <value>trainingHadoop01:2181,trainingHadoop02:2181,trainingHadoop03:2181,trainingHadoop04:2181</value> <description>各個ZK節點的IP/host,及客戶端連接ZK的端口,該端口需與zoo.cfg中的clientPort一致!</description>
</property>
</configuration>
<configuration>
<property>
<name>fs.defaultFS</name>
<value>hdfs://myCluster</value>
<description>注意:myhadoop爲集羣的邏輯名,最好與hdfs-site.xml中的dfs.nameservices配置一致!否則在使用hdfs命令的時候,後面跟的路徑就要指定全路徑.如果不一致,那麼執行hdfs
dfs -ls /就會報錯(java.net.UnknownHostException: ××××)。但可以通過這樣的命令來執行:hdfs
dfs -ls hdfs://myCluster
</description>
</property>
<property>
<name>ha.zookeeper.quorum</name>
<value>trainingHadoop01:2181,trainingHadoop02:2181,trainingHadoop03:2181,trainingHadoop04:2181</value>
<description>各個ZK節點的IP/host,及客戶端連接ZK的端口,該端口需與zoo.cfg中的clientPort一致!</description>
</property>
</configuration>
修改hdfs-site.xml
<property>
<name>dfs.ha.automatic-failover.enabled</name>
<value>true</value>
<description>
Whether automatic failover is enabled. See the HDFS High
Availability documentation for details on automatic HA
configuration.
</description>
</property>
<property>
<name>dfs.nameservices</name>
<value>myCluster</value>
<description>
Comma-separated list of nameservices.
</description>
</property>
<property>
<name>dfs.ha.namenodes.myCluster</name>
<value>nn1,nn2</value>
<description>
The prefix for a given nameservice, contains a
comma-separated
list of namenodes for a given nameservice (eg
EXAMPLENAMESERVICE).
</description>
</property>
<property>
<name>dfs.namenode.rpc-address.myCluster.nn1</name>
<value>trainingHadoop01:8020</value>
</property>
<property>
<name>dfs.namenode.rpc-address.myCluster.nn2</name>
<value>trainingHadoop02:8020</value>
</property>
<property>
<name>dfs.namenode.http-address.myCluster.nn1</name>
<value>trainingHadoop01:50070</value>
</property>
<property>
<name>dfs.namenode.http-address.myCluster.nn2</name>
<value>trainingHadoop02:50070</value>
</property>
<property>
<name>dfs.namenode.servicerpc-address.myCluster.nn1</name>
<value>trainingHadoop01:53310</value>
</property>
<property>
<name>dfs.namenode.servicerpc-address.myCluster.nn2</name>
<value>trainingHadoop02:53310</value>
</property>
<property>
<name>dfs.namenode.shared.edits.dir</name>
<value>qjournal://trainingHadoop02:8485;trainingHadoop03:8485;trainingHadoop04:8485/myCluster
</value>
</property>
<property>
<name>dfs.ha.fencing.methods</name>
<value>shell(/bin/true)</value>
<description>how to communicate in the switch process</description>
</property>
<property>
<name>dfs.ha.fencing.ssh.private-key-files</name>
<value>/home/hadoop/.ssh/id_rsa</value>
<description>the location stored ssh key</description>
</property>
<property>
<name>dfs.ha.fencing.ssh.connect-timeout</name>
<value>1000</value>
</property>
<property>
<name>dfs.namenode.handler.count</name>
<value>8</value>
</property>
<property>
<name>dfs.journalnode.edits.dir</name>
<value>/home/hadoop/hadoop-2.4.0/journal/</value>
</property>
<property>
<name>dfs.client.failover.proxy.provider.myCluster</name>
<value>org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider
</value>
</property>
三、配置文件同步到其他集羣中。
四、任意ZK節點上執行:
hdfs zkfc -formatZK
五、啓動ZKFC (ZookeeperFailoverController是用來監控NN狀態,協助實現主備NN切換的,所以僅僅在主備NN節點上啓動就行)
hadoop-daemon.sh start zkfc
啓動後我們可以看到ZKFC進程:[hadoop@trainingHadoop01 ~]$ jps
3084 QuorumPeerMain
3292 Jps
3247 DFSZKFailoverController
六、啓動用於主備NN之間同步元數據信息的共享存儲系統JournalNode。在集羣中各個節點上執行。
hadoop-daemon.sh start journalnode
[hadoop@trainingHadoop01 ~]$ jps
3084 QuorumPeerMain
3358 Jps
3325 JournalNode
3247 DFSZKFailoverController
七、格式化並啓動主NN
hdfs namenode -format
注意:只有第一次啓動系統時需格式化,請勿重複格式化!
在主NN節點執行命令啓動NN:
hadoop-daemon.sh start namenode
啓動後可以看到NN進程:
[hadoop@trainingHadoop01 ~]$ jps
3084 QuorumPeerMain
3480 Jps
3325 JournalNode
3411 NameNode
3247 DFSZKFailoverController
八、在備NN上同步主NN的元數據信息
hdfs namenode -bootstrapStandby
九、啓動備NN
在備NN上執行命令:
hadoop-daemon.sh start namenode
十、設置主NN(這一步可以省略,這是在設置手動切換NN時的步驟,ZK已經自動選擇一個節點作爲主NN了)
到目前爲止,其實HDFS還不知道誰是主NN,可以通過監控頁面查看,兩個節點的NN都是Standby狀態。
下面我們需要在主NN節點上執行命令激活主NN:
hdfs haadmin -transitionToActive nn1
十一、主NN上啓動Datanode
在[nn1]上,啓動所有datanode
hadoop-daemons.sh start datanode
所有節點啓動完成後,驗證主備切換。
首先打開地址:
http://10.21.16.48:50070/dfshealth.html#tab-overview
Overview 'trainingHadoop02:8020' (standby)
http://10.21.16.47:50070/dfshealth.html#tab-overview
Overview 'trainingHadoop01:8020' (active)
這個時候kill 掉trainingHadoop01 機器上的namenode進程。
刷新http://10.21.16.48:50070/dfshealth.html#tab-overview 這個地址。展示的是
Overview 'trainingHadoop02:8020' (active)
可能出現的問題:
Standby NN continuing as standby when active NN machine got shutdown.---這是個bug.在hadoop-2.4.0上,不過可以通過配置來解決這個問題。
<property>
<name>dfs.ha.fencing.methods</name>
<value>shell(/bin/true)</value>
</property>
Yarn的ResourceManage的HA配置
主要是修改yarn-site.xml
<property>
<name>yarn.resourcemanager.ha.enabled</name>
<value>true</value>
</property>
<property>
<description>Enable automatic failover.
By default, it is enabled only when HA is enabled
</description>
<name>yarn.resourcemanager.ha.automatic-failover.enabled</name>
<value>true</value>
</property>
<property>
<name>yarn.resourcemanager.ha.rm-ids</name>
<value>rm1,rm2</value>
</property>
<property>
<name>yarn.resourcemanager.zk-address</name>
<value>trainingHadoop01:2181,trainingHadoop02:2181,trainingHadoop03:2181
</value>
</property>
<property>
<name>yarn.resourcemanager.hostname.rm1</name>
<value>trainingHadoop01</value>
</property>
<property>
<name>yarn.resourcemanager.hostname.rm2</name>
<value>trainingHadoop02</value>
</property>
<property>
<name>yarn.resourcemanager.ha.id</name>
<value>rm1</value>
<description>If we want to launch more than one RM in single node, we
need this configuration</description>
</property>
<!開啓自動恢復功能>
<property>
<name>yarn.resourcemanager.recovery.enabled</name>
<value>true</value>
</property>
<property>
<name>yarn.resourcemanager.store.class</name>
<value>org.apache.hadoop.yarn.server.resourcemanager.recovery.ZKRMStateStore
</value>
</property>
<property>
<name>yarn.resourcemanager.cluster-id</name>
<value>yarn-cluster</value>
</property>
將修改後的配置文件yarn-site.xml同步到集羣中另外一臺機器上。
啓動,yarn-daemon.sh start resourcemanager
訪問http://trainingHadoop01:8088/
展示的是active的頁面
在備用機器上也啓動resourcemanager.
訪問http://trainingHadoop01:8088/
展示的是standby的頁面This is standby RM. Redirecting to the current active RM: http://trainingHadoop02:8088/cluster
然後會自動跳轉到active的地址。
自動切換驗證:
將active的機器的resourcemanager的進程kill掉。
standby的備用的機器變爲active。