hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1956) Export HDFS read and write latency as a metric
Date Thu, 05 Nov 2009 20:36:32 GMT

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

stack commented on HBASE-1956:
------------------------------

@Eli: My guess is that this would be an hbase metric.  We measure the time an append to our
WAL file takes.  If > a second, we recently started logging it as the canary for pending
hdfs issues.  I'm guessing Andrew is suggesting we add this to our list of hbase metrics.

> Export HDFS read and write latency as a metric
> ----------------------------------------------
>
>                 Key: HBASE-1956
>                 URL: https://issues.apache.org/jira/browse/HBASE-1956
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Priority: Minor
>             Fix For: 0.20.2, 0.21.0
>
>
> HDFS write latency spikes especially are an indicator of general cluster overloading.
We see this where the WAL writer complains about writes taking > 1 second, sometimes >
4, etc.  If for example the average write latency over the monitoring period is exported as
a metric, then this can feed into alerting for or automatic provisioning of additional cluster
hardware. While we're at it, export read side metrics as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message