hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16302) age of last shipped op and age of last applied op should be histograms
Date Tue, 29 Nov 2016 11:32:59 GMT

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

Hudson commented on HBASE-16302:

SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #2040 (See [https://builds.apache.org/job/HBase-Trunk_matrix/2040/])
HBASE-16302 age of last shipped op and age of last applied op should be (ashishsinghi: rev
* (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/MutableHistogram.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-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/MetricsSource.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

View raw message