hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Drzal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6974) Metric for blocked updates
Date Wed, 17 Oct 2012 15:38:05 GMT

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

Michael Drzal commented on HBASE-6974:
--------------------------------------

I think I addressed all of your concerns except for the placement of currentTimeMillis.  Let
me know if I understood you correctly, and if so, I can make the switch.
                
> Metric for blocked updates
> --------------------------
>
>                 Key: HBASE-6974
>                 URL: https://issues.apache.org/jira/browse/HBASE-6974
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>            Assignee: Michael Drzal
>            Priority: Critical
>             Fix For: 0.94.3, 0.96.0
>
>         Attachments: HBASE-6974.patch, HBASE-6974-v2.patch
>
>
> When the disc subsystem cannot keep up with a sustained high write load, a region will
eventually block updates to throttle clients.
> (HRegion.checkResources).
> It would be nice to have a metric for this, so that these occurrences can be tracked.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message