<?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 Hbase master crashing after startup in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hbase-master-crashing-after-startup/m-p/120844#M51171</link>
    <description>&lt;P&gt;I wander if any one has a solution or at least point me in the right direction.&lt;/P&gt;&lt;P&gt;Recent;y I did an upgrade of entire stack; Ambari from v. 2.2.2.0 to 2.4.2.0 and HPD from 2.4.2.0 to 2.5.3.0&lt;/P&gt;&lt;P&gt;Upgrade went more or less ok, but now my Hbase master falls over after about 30-35 sec. &lt;/P&gt;&lt;P&gt;this is the message I get in the log&lt;/P&gt; 2017-01-05 11:20:54,000 INFO  [main] util.ByteBufferArray: Allocating buffers total=10 GB, sizePerBuffer=4 MB, count=2560, direct=true&lt;P&gt;2017-01-05 11:20:54,695 ERROR [main] master.HMasterCommandLine: Master exiting
java.lang.RuntimeException: Failed construction of Master: class org.apache.hadoop.hbase.master.HMaster
at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2515)
at org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:235)
at org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
at org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2529)
Caused by: java.lang.OutOfMemoryError: Direct buffer memory
at java.nio.Bits.reserveMemory(Bits.java:658)
at java.nio.DirectByteBuffer.&amp;lt;init&amp;gt;(DirectByteBuffer.java:123)
at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
at org.apache.hadoop.hbase.util.ByteBufferArray.&amp;lt;init&amp;gt;(ByteBufferArray.java:65)
at org.apache.hadoop.hbase.io.hfile.bucket.ByteBufferIOEngine.&amp;lt;init&amp;gt;(ByteBufferIOEngine.java:47)
at org.apache.hadoop.hbase.io.hfile.bucket.BucketCache.getIOEngineFromName(BucketCache.java:307)
at org.apache.hadoop.hbase.io.hfile.bucket.BucketCache.&amp;lt;init&amp;gt;(BucketCache.java:217)
at org.apache.hadoop.hbase.io.hfile.CacheConfig.getBucketCache(CacheConfig.java:614)
at org.apache.hadoop.hbase.io.hfile.CacheConfig.getL2(CacheConfig.java:553)
at org.apache.hadoop.hbase.io.hfile.CacheConfig.instantiateBlockCache(CacheConfig.java:637)
at org.apache.hadoop.hbase.io.hfile.CacheConfig.&amp;lt;init&amp;gt;(CacheConfig.java:231)
at org.apache.hadoop.hbase.regionserver.HRegionServer.&amp;lt;init&amp;gt;(HRegionServer.java:564)
at org.apache.hadoop.hbase.master.HMaster.&amp;lt;init&amp;gt;(HMaster.java:411)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:25&lt;/P&gt;&lt;P&gt;this is exactly the same as &lt;A href="https://issues.apache.org/jira/browse/AMBARI-18238?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%202.4.1%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC"&gt;https://issues.apache.org/jira/browse/AMBARI-18238?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%202.4.1%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Having said that the bug reports stated it was addressed at 2.4.1 and I'm at 2.4.2&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Tue, 10 Jan 2017 05:50:21 GMT</pubDate>
    <dc:creator>ogorodet</dc:creator>
    <dc:date>2017-01-10T05:50:21Z</dc:date>
    <item>
      <title>Hbase master crashing after startup</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hbase-master-crashing-after-startup/m-p/120844#M51171</link>
      <description>&lt;P&gt;I wander if any one has a solution or at least point me in the right direction.&lt;/P&gt;&lt;P&gt;Recent;y I did an upgrade of entire stack; Ambari from v. 2.2.2.0 to 2.4.2.0 and HPD from 2.4.2.0 to 2.5.3.0&lt;/P&gt;&lt;P&gt;Upgrade went more or less ok, but now my Hbase master falls over after about 30-35 sec. &lt;/P&gt;&lt;P&gt;this is the message I get in the log&lt;/P&gt; 2017-01-05 11:20:54,000 INFO  [main] util.ByteBufferArray: Allocating buffers total=10 GB, sizePerBuffer=4 MB, count=2560, direct=true&lt;P&gt;2017-01-05 11:20:54,695 ERROR [main] master.HMasterCommandLine: Master exiting
java.lang.RuntimeException: Failed construction of Master: class org.apache.hadoop.hbase.master.HMaster
at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2515)
at org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:235)
at org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
at org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2529)
Caused by: java.lang.OutOfMemoryError: Direct buffer memory
at java.nio.Bits.reserveMemory(Bits.java:658)
at java.nio.DirectByteBuffer.&amp;lt;init&amp;gt;(DirectByteBuffer.java:123)
at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
at org.apache.hadoop.hbase.util.ByteBufferArray.&amp;lt;init&amp;gt;(ByteBufferArray.java:65)
at org.apache.hadoop.hbase.io.hfile.bucket.ByteBufferIOEngine.&amp;lt;init&amp;gt;(ByteBufferIOEngine.java:47)
at org.apache.hadoop.hbase.io.hfile.bucket.BucketCache.getIOEngineFromName(BucketCache.java:307)
at org.apache.hadoop.hbase.io.hfile.bucket.BucketCache.&amp;lt;init&amp;gt;(BucketCache.java:217)
at org.apache.hadoop.hbase.io.hfile.CacheConfig.getBucketCache(CacheConfig.java:614)
at org.apache.hadoop.hbase.io.hfile.CacheConfig.getL2(CacheConfig.java:553)
at org.apache.hadoop.hbase.io.hfile.CacheConfig.instantiateBlockCache(CacheConfig.java:637)
at org.apache.hadoop.hbase.io.hfile.CacheConfig.&amp;lt;init&amp;gt;(CacheConfig.java:231)
at org.apache.hadoop.hbase.regionserver.HRegionServer.&amp;lt;init&amp;gt;(HRegionServer.java:564)
at org.apache.hadoop.hbase.master.HMaster.&amp;lt;init&amp;gt;(HMaster.java:411)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:25&lt;/P&gt;&lt;P&gt;this is exactly the same as &lt;A href="https://issues.apache.org/jira/browse/AMBARI-18238?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%202.4.1%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC"&gt;https://issues.apache.org/jira/browse/AMBARI-18238?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%202.4.1%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Having said that the bug reports stated it was addressed at 2.4.1 and I'm at 2.4.2&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 10 Jan 2017 05:50:21 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hbase-master-crashing-after-startup/m-p/120844#M51171</guid>
      <dc:creator>ogorodet</dc:creator>
      <dc:date>2017-01-10T05:50:21Z</dc:date>
    </item>
    <item>
      <title>Re: Hbase master crashing after startup</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hbase-master-crashing-after-startup/m-p/120845#M51172</link>
      <description>&lt;P&gt;Hello. If you're not using Off-heap memory (Bucketcache) you can try disabling the 3 configuration properties and 1 environment variable setting that gets added during the Ambari upgrade.&lt;/P&gt;&lt;PRE&gt;Using Ambari, modify your Hbase configuration and blank the following:
hbase.bucketcache.size
hbase.bucketcache.ioengine
hbase.bucketcache.percentage.in.combinedcache

Modify hbase-env template:
comment out line: export HBASE_REGIONSERVER_OPTS = ... -XX:MaxDirectMemorySize

Restart all affected&lt;/PRE&gt;</description>
      <pubDate>Tue, 10 Jan 2017 07:09:14 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hbase-master-crashing-after-startup/m-p/120845#M51172</guid>
      <dc:creator>jyoung</dc:creator>
      <dc:date>2017-01-10T07:09:14Z</dc:date>
    </item>
    <item>
      <title>Re: Hbase master crashing after startup</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hbase-master-crashing-after-startup/m-p/120846#M51173</link>
      <description>&lt;P&gt;That did the trick... thanks&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jan 2017 04:49:34 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hbase-master-crashing-after-startup/m-p/120846#M51173</guid>
      <dc:creator>ogorodet</dc:creator>
      <dc:date>2017-01-11T04:49:34Z</dc:date>
    </item>
    <item>
      <title>Re: Hbase master crashing after startup</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hbase-master-crashing-after-startup/m-p/120847#M51174</link>
      <description>&lt;P&gt;I'm happy to hear that worked out for you. Feel free to accept the answer if you're happy with it.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jan 2017 05:54:01 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hbase-master-crashing-after-startup/m-p/120847#M51174</guid>
      <dc:creator>jyoung</dc:creator>
      <dc:date>2017-01-11T05:54:01Z</dc:date>
    </item>
  </channel>
</rss>

