[
https://issues.apache.org/jira/browse/HBASE-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008306#comment-13008306
]
stack commented on HBASE-3658:
------------------------------
That sounds right Subbu. I see it as a utility method on HBaseConfiguration.
You'd pass a method named 'check' or 'checkIsWholesome" or something and it
would run what you describe above. Later we might add other checks beyond the
two above.
> 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
>
>
> 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
