[HBASE-11143] Improve replication metrics

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.99.0, 0.94.20, 0.98.3
• Component/s: Replication
• Hadoop Flags: Reviewed
• Assignee: Lars Hofhansl
• Reporter: Lars Hofhansl
• Created: 09/May/14 00:53
• Updated: 05/Aug/14 03:36
• Resolved: 14/May/14 06:20

Description

We are trying to report on replication lag and find that there is no good single metric to do that.
ageOfLastShippedOp is close, but unfortunately it is increased even when there is nothing to ship on a particular RegionServer.

I would like discuss a few options here:
Add a new metric: replicationQueueTime (or something) with the above meaning. I.e. if we have something to ship we set the age of that last shipped edit, if we fail we increment that last time (just like we do now). But if there is nothing to replicate we set it to current time (and hence that metric is reported to close to 0).
Alternatively we could change the meaning of ageOfLastShippedOp to mean to do that. That might lead to surprises, but the current behavior is clearly weird when there is nothing to replicate.

Comments? jdcryans, stack.

If approach sounds good, I'll make a patch for all branches.

Edit: Also adds a new shippedKBs metric to track the amount of data that is shipped via replication.

Issue Links

• is related to: HBASE-9286 [0.94] ageOfLastShippedOp replication metric doesn't update if the slave regionserver is stalled
• relates to: HBASE-11597 Document new metric shippedKBs
• relates to: HBASE-11617 incorrect AgeOfLastAppliedOp and AgeOfLastShippedOp in replication Metrics when no new replication OP