[
https://issues.apache.org/jira/browse/HBASE-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475964#comment-13475964
]
Anoop Sam John commented on HBASE-6974:
---------------------------------------
Lars
Updates will be blocked because more than one reason right
1. As in checkResources when the memstore size became too much (as per the
hbase.hregion.memstore.block.multiplier value and memstore size)
2. Because of the global heap space usage for all the memstore in the RS
3. Becuase of the store files count being more
(hbase.hstore.blockingStoreFiles).. Well this is not directly affect.. This
will make the flush to wait which in turn can block the updates also as per the
point 1.. So may be not to consider..
So your idea is that in all case where the block is happened the wait time will
be captured and updated in the metric right? May be reason also we can capture
so that after seeing this metric user can think about changing some configs if
needed etc...
Just for confirming I asked.. Will be very much useful I guess...
Nice work Lars... We would like to use this...
> 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
>
>
> 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
