hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashu Pachauri (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-16302) age of last shipped op is not representative for multiwal
Date Thu, 06 Oct 2016 23:00:26 GMT

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

Ashu Pachauri updated HBASE-16302:
----------------------------------
    Description: 
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.

  was:
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.

An example improvement can be providing age of last shipped op per wal group.


> age of last shipped op is not representative for multiwal
> ---------------------------------------------------------
>
>                 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)

Mime
View raw message