[
https://issues.apache.org/jira/browse/HBASE-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141482#comment-13141482
]
stack commented on HBASE-3680:
------------------------------
I committed this patch already by mistake as part of this commit:
{code}
------------------------------------------------------------------------
r1195833 | stack | 2011-10-31 22:36:12 -0700 (Mon, 31 Oct 2011) | 1 line
HBASE-4703 Improvements in tests
{code}
I did all but the change to MemStore.java. Let me commit that now.
> Publish more metrics about mslab
> --------------------------------
>
> Key: HBASE-3680
> URL: https://issues.apache.org/jira/browse/HBASE-3680
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.90.1
> Reporter: Jean-Daniel Cryans
> Assignee: Todd Lipcon
> Fix For: 0.92.0
>
> Attachments: hbase-3680.txt, hbase-3680.txt
>
>
> We have been using mslab on all our clusters for a while now and it seems it
> tends to OOME or send us into GC loops of death a lot more than it used to.
> For example, one RS with mslab enabled and 7GB of heap died out of OOME this
> afternoon; it had .55GB in the block cache and 2.03GB in the memstores which
> doesn't account for much... but it could be that because of mslab a lot of
> space was lost in those incomplete 2MB blocks and without metrics we can't
> really tell. Compactions were running at the time of the OOME and I see block
> cache activity. The average load on that cluster is 531.
> We should at least publish the total size of all those blocks and maybe even
> take actions based on that (like force flushing).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
