hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asaf Mesika (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3680) Publish more metrics about mslab
Date Thu, 14 Nov 2013 09:05:23 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822261#comment-13822261

Asaf Mesika commented on HBASE-3680:

I fix you should reset fix-version field, since it's not really fixed and confusing.

> 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.3
>         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 was sent by Atlassian JIRA

View raw message