Hbase managed zookeeper suddenly trying to connect to localhost instead of zookeeper quorum

时光怂恿深爱的人放手 提交于 2019-12-01 05:25:04

I've had same problem when running HBase through Spark on Yarn. Everything was fine until suddenly it started to trying to connect to localhost instead of quorum. Setting port and quorum programmatically before HBase call fixed the issue

conf.set("hbase.zookeeper.quorum","my.server")
conf.set("hbase.zookeeper.property.clientPort","5181")

I'm using MapR, and it has "unusual" (5181) zookeeper port

Hard to say what is happening with the information, given. I have found the Hadoop Stack (HBase especially) to be quite hostile to even the slightest bit of misconfiguration in DNS or the hosts file.

As the quorum in your hbase-site.xml looks good, I'd start checking with network/hostname resolution related configurations:

  • Has the nodename slipped into the localhost entry in /etc/hosts on hdev03?
  • Is there an entry for the host itself in hdev03s /etc/hosts (there should)?
  • Has Reverse DNS been correctly configured in case you are using DNS for name resolution instead of the hosts file?

These are just a few pointers in the direction I'd look with this kind of issue. Hope it helps!

Add '--driver-class-path ~/hbase-1.1.2/conf' into spark-submit command, so that the task can find the configured zookeeper servers instead of 127.0.0.1.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!