You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Ashu Pachauri (JIRA)" <ji...@apache.org> on 2016/11/21 22:48:58 UTC

[jira] [Updated] (HBASE-16302) age of last shipped op and age of last applied op should be a histogram

     [ https://issues.apache.org/jira/browse/HBASE-16302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashu Pachauri updated HBASE-16302:
----------------------------------
    Summary: age of last shipped op and age of last applied op should be a histogram  (was: age of last shipped op is not representative for multiwal)

> age of last shipped op and age of last applied op should be a histogram
> -----------------------------------------------------------------------
>
>                 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
>
> 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.
> We should just report the maximum of the age of last shipped ops across walgroups.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)