ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-11552) 2.3 stack advisor doesn't take into account HBASE-11520
Date Thu, 04 Jun 2015 02:23:39 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-11552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571989#comment-14571989
] 

Hudson commented on AMBARI-11552:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #2804 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2804/])
AMBARI-11552. 2.3 stack advisor doesn't take into account HBASE-11520 (Nick Dimiduk via srimanth)
(sgunturi: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=aeccbc7fe458509241e16c47f653f65a6ed8c2e4)
* ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py
* ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py


> 2.3 stack advisor doesn't take into account HBASE-11520
> -------------------------------------------------------
>
>                 Key: AMBARI-11552
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11552
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Nick Dimiduk
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11552.00.patch, AMBARI-11552.patch
>
>
> Launching a HDP-2.3 RS with the HDP-2.2 stack_advisor's output on a machine with lots
of ram results in
> {noformat}
> regionserver.HRegionServer: Failed init
> java.lang.OutOfMemoryError: Direct buffer memory
> at java.nio.Bits.reserveMemory(Bits.java:658)
> at java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:123)
> at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
> at org.apache.hadoop.hbase.util.ByteBufferArray.<init>(ByteBufferArray.java:65)
> at org.apache.hadoop.hbase.io.hfile.bucket.ByteBufferIOEngine.<init>(ByteBufferIOEngine.java:47)
> at org.apache.hadoop.hbase.io.hfile.bucket.BucketCache.getIOEngineFromName(BucketCache.java:309)
> at org.apache.hadoop.hbase.io.hfile.bucket.BucketCache.<init>(BucketCache.java:219)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.getBucketCache(CacheConfig.java:568)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.getL2(CacheConfig.java:511)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.instantiateBlockCache(CacheConfig.java:591)
> at org.apache.hadoop.hbase.io.hfile.CacheConfig.<init>(CacheConfig.java:231)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.handleReportForDutyResponse(HRegionServer.java:1349)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:896)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> HBASE-11520 introduced a subtle change in the configuration, it's release note says
> bq. Remove "hbase.bucketcache.percentage.in.combinedcache". Simplifies config of block
cache. If you are using this config., after this patch goes in, it will be ignored. The L1
LruBlockCache will be whatever hfile.block.cache.size is set to and the L2 BucketCache will
be whatever hbase.bucketcache.size is set to.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message