[
https://issues.apache.org/jira/browse/HBASE-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008456#comment-13008456
]
Subbu M Iyer commented on HBASE-3658:
-------------------------------------
I verified that my cluster does not start when I have the sum of Memstore +
Blockcache allocation exceeds 0.8f.
$ ./start-hbase.sh
Exception in thread "main" java.lang.RuntimeException: Current heap
configuration for MemStore and BlockCache exceeds the threshold required for
successful cluster operation. The combined value cannot exceed 0.8. Please
check the settings for hbase.regionserver.global.memstore.upperLimit and
hfile.block.cache.size in your configuration.
at
org.apache.hadoop.hbase.HBaseConfiguration.checkForClusterFreeMemoryLimit(HBaseConfiguration.java:78)
at
org.apache.hadoop.hbase.HBaseConfiguration.addHbaseResources(HBaseConfiguration.java:91)
at
org.apache.hadoop.hbase.HBaseConfiguration.create(HBaseConfiguration.java:101)
at
org.apache.hadoop.hbase.util.HBaseConfTool.main(HBaseConfTool.java:38)
Exception in thread "main" java.lang.RuntimeException: Current heap
configuration for MemStore and BlockCache exceeds the threshold required for
successful cluster operation. The combined value cannot exceed 0.8. Please
check the settings for hbase.regionserver.global.memstore.upperLimit and
hfile.block.cache.size in your configuration.
at
org.apache.hadoop.hbase.HBaseConfiguration.checkForClusterFreeMemoryLimit(HBaseConfiguration.java:78)
at
org.apache.hadoop.hbase.HBaseConfiguration.addHbaseResources(HBaseConfiguration.java:91)
at
org.apache.hadoop.hbase.HBaseConfiguration.create(HBaseConfiguration.java:101)
at
org.apache.hadoop.hbase.zookeeper.ZKServerTool.main(ZKServerTool.java:39)
starting master, logging to
/work/hbase-0.90.1/bin/../logs/hbase-subbu-master-subbumac.local.out
Exception in thread "main" java.lang.RuntimeException: Current heap
configuration for MemStore and BlockCache exceeds the threshold required for
successful cluster operation. The combined value cannot exceed 0.8. Please
check the settings for hbase.regionserver.global.memstore.upperLimit and
hfile.block.cache.size in your configuration.
at
org.apache.hadoop.hbase.HBaseConfiguration.checkForClusterFreeMemoryLimit(HBaseConfiguration.java:78)
at
org.apache.hadoop.hbase.HBaseConfiguration.addHbaseResources(HBaseConfiguration.java:91)
at
org.apache.hadoop.hbase.HBaseConfiguration.create(HBaseConfiguration.java:101)
at
org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:76)
at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:1205)
localhost: starting regionserver, logging to
/work/hbase-0.90.1/bin/../logs/hbase-subbu-regionserver-subbumac.local.out
localhost: Exception in thread "main" java.lang.RuntimeException: Current heap
configuration for MemStore and BlockCache exceeds the threshold required for
successful cluster operation. The combined value cannot exceed 0.8. Please
check the settings for hbase.regionserver.global.memstore.upperLimit and
hfile.block.cache.size in your configuration.
localhost: at
org.apache.hadoop.hbase.HBaseConfiguration.checkForClusterFreeMemoryLimit(HBaseConfiguration.java:78)
localhost: at
org.apache.hadoop.hbase.HBaseConfiguration.addHbaseResources(HBaseConfiguration.java:91)
localhost: at
org.apache.hadoop.hbase.HBaseConfiguration.create(HBaseConfiguration.java:101)
localhost: at
org.apache.hadoop.hbase.regionserver.HRegionServer.main(HRegionServer.java:2815)
> Alert when heap is over committed
> ---------------------------------
>
> Key: HBASE-3658
> URL: https://issues.apache.org/jira/browse/HBASE-3658
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.90.1
> Reporter: Jean-Daniel Cryans
> Fix For: 0.92.0
>
> Attachments: HBASE-3658_Alert_when_heap_is_over_committed.patch
>
>
> Something I just witnessed, the block cache setting was at 70% but the max
> global memstore size was at the default of 40% meaning that 110% of the heap
> can potentially be "assigned" and then you need more heap to do stuff like
> flushing and compacting.
> We should run a configuration check that alerts the user when that happens
> and maybe even refuse to start.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
