[
https://issues.apache.org/jira/browse/HBASE-26581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528994#comment-17528994
]
Hudson commented on HBASE-26581:
--------------------------------
Results for branch master
[build #572 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/572/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/572/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/572/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/572/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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
> 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)
