[
https://issues.apache.org/jira/browse/HBASE-17531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848641#comment-15848641
]
Sean Busbey commented on HBASE-17531:
-------------------------------------
in branch-1 FSHLog will treat an undefined as "we are always at max number of
wals and need to flush now."
> Memory tuning should account for undefined max heap
> ---------------------------------------------------
>
> Key: HBASE-17531
> URL: https://issues.apache.org/jira/browse/HBASE-17531
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Reporter: Sean Busbey
>
> While going through HBASE-17522, I noticed that our calculations for heap
> usage don't account for the JVM returning a -1 to mean "undefined" for the
> max heap. for example, {{getOnheapGlobalMemstoreSize}} just does the
> calculation as it would if a normal number is returned, which means we end up
> with -1 or 0 and then the logic in
> {{RegionServerAccounting.isAboveHighWaterMark()}} is always going to say "we
> need to flush".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
