[
https://issues.apache.org/jira/browse/HBASE-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175163#comment-13175163
]
Mubarak Seyed commented on HBASE-3565:
--------------------------------------
IMO we need 4 metrics
1. slowHLogAppendsCount (AtomicLong, increment by 1 whenever it takes > 1 sec
to append HLog, no reset, long-live until RS runs)
2. minHLogAppendTime (when we log slow appends > 1 sec)
3. avgHLogAppendTime
4. maxHLogAppendTime
2, 3, and 4 are needs to get reset upon every doUpdate() for every 5 minutes or
so. For every 5 minutes, we will get 1 min/avg/max HLog append time.
> Add a metric to keep track of slow HLog appends
> -----------------------------------------------
>
> Key: HBASE-3565
> URL: https://issues.apache.org/jira/browse/HBASE-3565
> Project: HBase
> Issue Type: Improvement
> Components: metrics, regionserver
> Reporter: Benoit Sigoure
> Labels: monitoring
>
> Whenever an edit takes too long to be written to an HLog, HBase logs a
> warning such as this one:
> {code}
> 2011-02-23 20:03:14,703 WARN org.apache.hadoop.hbase.regionserver.wal.HLog:
> IPC Server handler 21 on 60020 took 15065ms appending an edit to hlog;
> editcount=126050
> {code}
> I would like to have a counter incremented each time this happens and this
> counter exposed via the metrics stuff in HBase so I can collect it in my
> monitoring system.
--
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
