首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >在/0.0.0.0:8032上连接到ResourceManager的Hadoop ResourceManager HA

在/0.0.0.0:8032上连接到ResourceManager的Hadoop ResourceManager HA
EN

Stack Overflow用户
提问于 2015-10-29 23:15:35
回答 1查看 2.1K关注 0票数 2

扩展其中一个问题:Hadoop: Connecting to ResourceManager failed

Hadoop 2.6.1

我配置了ResourceManager HA。

当我终止“本地”ResourceManager (以检查群集)时,故障转移发生,其他服务器上的ResourceManager变为活动状态。不幸的是,当我尝试使用“本地”实例nodemanager运行作业时,它没有将请求“故障转移”到active ResourceManager。

代码语言:javascript
复制
yarn@stg-hadoop106:~$ jps
26738 Jps
23463 DataNode
23943 DFSZKFailoverController
24297 NodeManager
25690 ResourceManager
23710 JournalNode
23310 NameNode

#kill and start ResourceManager, so the failover occur
yarn@stg-hadoop106:~$ kill -9 25690
~/hadoop/sbin/yarn-daemon.sh  start resourcemanager

yarn@stg-hadoop106:~$ ~/hadoop/bin/yarn  rmadmin -getServiceState rm1
standby
yarn@stg-hadoop106:~$ ~/hadoop/bin/yarn  rmadmin -getServiceState rm2
active

#run my class:

14:56:51.476 [main] INFO  o.apache.samza.job.yarn.ClientHelper - trying to connect to RM 0.0.0.0:8032
2015-10-29 14:56:51 RMProxy [INFO] Connecting to ResourceManager at /0.0.0.0:8032
14:56:51.572 [main] DEBUG o.a.h.s.a.util.KerberosName - Kerberos krb5 configuration not found, setting default realm to empty
2015-10-29 14:56:51 NativeCodeLoader [WARN] Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
14:56:51.575 [main] DEBUG o.a.hadoop.util.PerformanceAdvisory - Falling back to shell based
2015-10-29 14:56:52 Client [INFO] Retrying connect to server: 0.0.0.0/0.0.0.0:8032. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)
2015-10-29 14:56:53 Client [INFO] Retrying connect to server: 0.0.0.0/0.0.0.0:8032. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS)

yarn-site.xml

代码语言:javascript
复制
 <property>
     <name>yarn.resourcemanager.ha.enabled</name>
     <value>true</value>
 </property>
 <property>
     <name>yarn.resourcemanager.cluster-id</name>
     <value>clusterstaging</value>
 </property>
 <property>
     <name>yarn.resourcemanager.ha.rm-ids</name>
     <value>rm1,rm2,rm3</value>
 </property>
 <property>
     <name>yarn.resourcemanager.hostname.rm1</name>
     <value>stg-hadoop106</value>
 </property>
 <property>
     <name>yarn.resourcemanager.hostname.rm2</name>
     <value>stg-hadoop107</value>
 </property>
 <property>
     <name>yarn.resourcemanager.hostname.rm3</name>
     <value>stg-hadoop108</value>
 </property>
 <property>
     <name>yarn.resourcemanager.zk-address</name>
     <value>A:2181,B:2181,C:2181</value>
 </property>

我没有配置

代码语言:javascript
复制
<name>yarn.resourcemanager.hostname</name>

因为它应该“按原样”工作-如果我错了,请纠正我:)

我确实试过了

代码语言:javascript
复制
<name>yarn.client.failover-proxy-provider</name>

但没有成功

有什么想法吗?也许我错误地期望客户端找出活动RM节点?

您知道如何在“自动故障切换”选项中切换节点的活动/备用模式吗?

代码语言:javascript
复制
~/hadoop/bin/yarn  rmadmin -failover rm1 rm2
    Exception in thread "main" java.lang.UnsupportedOperationException: RMHAServiceTarget doesn't have a corresponding ZKFC address

~/hadoop/bin/yarn  rmadmin -transitionToActive rm1 rm2
    Automatic failover is enabled for org.apache.hadoop.yarn.client.RMHAServiceTarget@2b72cb8a
    Refusing to manually manage HA state, since it may cause
EN

回答 1

Stack Overflow用户

发布于 2015-10-30 19:00:59

如果在自动故障切换模式下启用HA-RM,则不能将活动状态触发为备用状态,反之亦然。并且您应该提供yarn.client.failover-proxy-provider参数,这是客户端用来故障转移到活动RM的类。以及配置yarn.resourcemanager.hostname以识别RM(即,rm1、rm2)。

如果未启用自动故障转移,您可以使用以下yarn rmadmin -transitionToStandby rm1触发

请做上述更改,并回复结果

票数 0
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/33418065

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档