hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16302) age of last shipped op and age of last applied op should be histograms
Date Thu, 09 Mar 2017 20:17:38 GMT

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

Hadoop QA commented on HBASE-16302:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s {color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 6s {color} | {color:red}
HBASE-16302 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.3.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12839904/HBASE-16302.patch.v0.patch
|
| JIRA Issue | HBASE-16302 |
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/6044/console |
| Powered by | Apache Yetus 0.3.0   http://yetus.apache.org |


This message was automatically generated.



> 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)

Mime
View raw message