[
https://issues.apache.org/jira/browse/HBASE-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477905#comment-13477905
]
Michael Drzal commented on HBASE-6974:
--------------------------------------
[~lhofhansl]
- 1024 ms to s conversion fixed. I think I spent too much time converting
bytes around, sorry
- I'll add in the memstore flusher metric and post a patch in a bit
- I'll look into EnvironmentEdge.currentTimeMillis
- I understand what you are saying about currentTimeMillis, but let me try to
restate what you said so that I am sure that we are on the same page:
If I move the call to currentTimeMillis inside the while loop, that means that
I will have to keep another variable off to the side to keep track of the
total, plus another one to accomplish the swap. Doing this, I would call
currentTimeMillis once for each time through the loop, correct? If you think
that is a better way to go, I can do that.
> 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
>
>
> 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
