[
https://issues.apache.org/jira/browse/HBASE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650288#action_12650288
]
Andrew Purtell commented on HBASE-1018:
---------------------------------------
I tried using Runtime. Seemed no good way to get a good read on 'used'. The
MBean gets it right and the JRE >= 5.0 includes everything needed.
Runtime.getRuntime().maxMemory behaved as you'd expect.
Runtime.getRuntime().freeMemory would start off in the single digits and climb.
Runtime.getRuntime().totalMemory didn't look right either.
> Regionservers should report detailed health to master; master should flag
> troubled regionservers in UI
> ------------------------------------------------------------------------------------------------------
>
> Key: HBASE-1018
> URL: https://issues.apache.org/jira/browse/HBASE-1018
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: master, regionserver
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.19.0
>
> Attachments: 1018.patch
>
>
> Regionservers should report detailed health to master. The master should flag
> troubled regionservers in the UI.
> The concern at the moment is primarily heap. Regionservers should report
> used, committed, and max heap metrics in the periodic report. The master
> should flag in the regionserver list on /master.jsp those regionservers where
> available heap is below a configurable threshold.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
