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

Hudson commented on HBASE-16302:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-1.3-IT #6 (See 
[https://builds.apache.org/job/HBase-1.3-IT/6/])
HBASE-17579 Backport HBASE-16302 to 1.3.1 (garyh: rev 
d74b7270852289c2d05f139b1142f034f9348897)
* (edit) 
hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/replication/regionserver/MetricsReplicationSourceSourceImpl.java
* (edit) 
hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/DynamicMetricsRegistry.java
* (edit) 
hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/replication/regionserver/MetricsReplicationGlobalSourceSource.java
* (edit) 
hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/replication/regionserver/MetricsReplicationSinkSourceImpl.java
* (edit) 
hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/MutableHistogram.java


> age of last shipped op and age of last applied op should be histograms
> ----------------------------------------------------------------------
>
>                 Key: HBASE-16302
>                 URL: https://issues.apache.org/jira/browse/HBASE-16302
>             Project: HBase
>          Issue Type: Improvement
>          Components: Replication
>            Reporter: Ashu Pachauri
>            Assignee: Ashu Pachauri
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: HBASE-16302.patch.v0.patch
>
>
> Replication exports metric ageOfLastShippedOp as an indication of how much 
> replication is lagging. But, with multiwal enabled, it's not representative 
> because replication could be lagging for a long time for one wal group 
> (something wrong with a particular region) while being fine for others. The 
> ageOfLastShippedOp becomes a useless metric for alerting in such a case.
> Also, since there is no mapping between individual replication sources and 
> replication sinks, the age of last applied op can be a highly spiky metric if 
> only certain replication sources are lagging.
> We should use histograms for these metrics and use maximum value of this 
> histogram to report replication lag when building stats.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to