[
https://issues.apache.org/jira/browse/HBASE-26581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Beaudreault updated HBASE-26581:
--------------------------------------
Fix Version/s: 3.0.0-alpha-3
2.4.12
Release Note: Adds new metrics sink.failedBatches and source.failedBatches
to replication metrics, allowing one to track failures on both sides of a
replication stream. As with other source metrics, the new source.failedBatches
is reported globally and by peer id.
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for contributing [~baugenreich] and thanks for reviewing [~apurtell]!
Committed to master, branch-2, branch-2.4, and branch-2.5
> Add metrics around failed replication edits
> -------------------------------------------
>
> Key: HBASE-26581
> URL: https://issues.apache.org/jira/browse/HBASE-26581
> Project: HBase
> Issue Type: Improvement
> Components: metrics, Replication
> Reporter: Bryan Beaudreault
> Assignee: Briana Augenreich
> Priority: Minor
> Labels: patch-available
> Fix For: 3.0.0-alpha-3, 2.4.12
>
>
> We ran into HBASE-26575 recently, but had a hard time tracking down where the
> edits were coming from. The only real evidence of a failure in replication
> was the ageOfLastShipped metric and some warnings in the logs. It would be
> nice to add an explicit metric around source.failedBatches and
> sink.failedBatches, incremented whenever an exception is encountered.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
