<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: HBase Region Servers Startup Failed after Namenode HA in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-Region-Servers-Startup-Failed-after-Namenode-HA/m-p/211678#M78806</link>
    <description>&lt;P&gt;Looks like Hadoop configurations was missing under classpath and it is not able to detect the nameservice.&lt;/P&gt;&lt;P&gt;Can you check hbase config directory on working region server and non-working region server whether there are missing core-site.xml or hdfs-site.xml files?&lt;/P&gt;</description>
    <pubDate>Tue, 29 May 2018 20:14:18 GMT</pubDate>
    <dc:creator>schhabra1</dc:creator>
    <dc:date>2018-05-29T20:14:18Z</dc:date>
    <item>
      <title>HBase Region Servers Startup Failed after Namenode HA</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-Region-Servers-Startup-Failed-after-Namenode-HA/m-p/211677#M78805</link>
      <description>&lt;P&gt;After Namenode HA, 2 out of my 3 Region Servers in HBase are not coming up. I looked at the logs and found that it is throwing unknown host exception for name service.&lt;/P&gt;&lt;PRE&gt;2018-05-24 08:48:29,551 INFO  [regionserver/atlhashdn02.hashmap.net/192.166.4.37:16020] regionserver.HRegionServer: STOPPED: Failed initialization
2018-05-24 08:48:29,552 ERROR [regionserver/atlhashdn02.hashmap.net/192.166.4.37:16020] regionserver.HRegionServer: Failed init
java.lang.IllegalArgumentException: java.net.UnknownHostException: clusterha
        at org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:411)
        at org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:311)
        at org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176)
        at org.apache.hadoop.hdfs.DFSClient.&amp;lt;init&amp;gt;(DFSClient.java:688)
        at org.apache.hadoop.hdfs.DFSClient.&amp;lt;init&amp;gt;(DFSClient.java:629)
        at org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:159)
        at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2761)
        at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99)
        at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2795)
        at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2777)
        at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:386)
        at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:179)
        at org.apache.hadoop.hbase.wal.DefaultWALProvider.init(DefaultWALProvider.java:97)
        at org.apache.hadoop.hbase.wal.WALFactory.getProvider(WALFactory.java:148)
        at org.apache.hadoop.hbase.wal.WALFactory.&amp;lt;init&amp;gt;(WALFactory.java:180)
        at org.apache.hadoop.hbase.regionserver.HRegionServer.setupWALAndReplication(HRegionServer.java:1648)
        at org.apache.hadoop.hbase.regionserver.HRegionServer.handleReportForDutyResponse(HRegionServer.java:1381)
        at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:917)
        at java.lang.Thread.run(Thread.java:745)
&lt;/PRE&gt;</description>
      <pubDate>Mon, 28 May 2018 14:00:44 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-Region-Servers-Startup-Failed-after-Namenode-HA/m-p/211677#M78805</guid>
      <dc:creator>sparsh_singhal</dc:creator>
      <dc:date>2018-05-28T14:00:44Z</dc:date>
    </item>
    <item>
      <title>Re: HBase Region Servers Startup Failed after Namenode HA</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-Region-Servers-Startup-Failed-after-Namenode-HA/m-p/211678#M78806</link>
      <description>&lt;P&gt;Looks like Hadoop configurations was missing under classpath and it is not able to detect the nameservice.&lt;/P&gt;&lt;P&gt;Can you check hbase config directory on working region server and non-working region server whether there are missing core-site.xml or hdfs-site.xml files?&lt;/P&gt;</description>
      <pubDate>Tue, 29 May 2018 20:14:18 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-Region-Servers-Startup-Failed-after-Namenode-HA/m-p/211678#M78806</guid>
      <dc:creator>schhabra1</dc:creator>
      <dc:date>2018-05-29T20:14:18Z</dc:date>
    </item>
    <item>
      <title>Re: HBase Region Servers Startup Failed after Namenode HA</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-Region-Servers-Startup-Failed-after-Namenode-HA/m-p/211679#M78807</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/18485/schhabra.html" nodeid="18485"&gt;@schhabra&lt;/A&gt; &lt;/P&gt;&lt;P&gt;I checked hbase-site.xml, hdfs-site.xml and core-site.xml. They are exactly same on both nodes.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Jun 2018 16:45:30 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-Region-Servers-Startup-Failed-after-Namenode-HA/m-p/211679#M78807</guid>
      <dc:creator>sparsh_singhal</dc:creator>
      <dc:date>2018-06-01T16:45:30Z</dc:date>
    </item>
    <item>
      <title>Re: HBase Region Servers Startup Failed after Namenode HA</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-Region-Servers-Startup-Failed-after-Namenode-HA/m-p/211680#M78808</link>
      <description>&lt;P&gt;Well, the configuration files were correct, but the environment was not set properly. Checked hbase env on both nodes and found a difference. Update with the following properties in ambari and it worked:&lt;/P&gt;&lt;PRE&gt;export LD_LIBRARY_PATH=::/usr/hdp/2.6.3.0-235/hadoop/lib/native/Linux-amd64-64:/usr/lib/hadoop/lib/native/Linux-amd64-64:/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64:/usr/hdp/2.6.3.0-235/hadoop/lib/native
export HADOOP_HOME=/usr/hdp/2.6.3.0-235/hadoop
export HADOOP_CONF_DIR=/usr/hdp/2.6.3.0-235/hadoop/etc/hadoop&lt;BR /&gt;&lt;/PRE&gt;</description>
      <pubDate>Sat, 02 Jun 2018 19:39:37 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-Region-Servers-Startup-Failed-after-Namenode-HA/m-p/211680#M78808</guid>
      <dc:creator>sparsh_singhal</dc:creator>
      <dc:date>2018-06-02T19:39:37Z</dc:date>
    </item>
  </channel>
</rss>

