[
https://issues.apache.org/jira/browse/HBASE-26913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631362#comment-17631362
]
Hudson commented on HBASE-26913:
--------------------------------
Results for branch branch-2
[build #677 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/677/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/677/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/677/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/677/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/branch-2/677/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}
> Replication Observability Framework
> -----------------------------------
>
> Key: HBASE-26913
> URL: https://issues.apache.org/jira/browse/HBASE-26913
> Project: HBase
> Issue Type: New Feature
> Components: regionserver, Replication
> Reporter: Rushabh Shah
> Assignee: Rushabh Shah
> Priority: Major
> Fix For: 2.6.0, 3.0.0-alpha-4
>
>
> In our production clusters, we have seen cases where data is present in
> source cluster but not in the sink cluster and 1 case where data is present
> in sink cluster but not in source cluster.
> We have internal tools where we take incremental backup every day on both
> source and sink clusters and we compare the hash of the data in both the
> backups. We have seen many cases where hash doesn't match which means data is
> not consistent between source and sink for that given day. The Mean Time To
> Detect (MTTD) these inconsistencies is atleast 2 days and requires lot of
> manual debugging.
> We need some tool where we can reduce MTTD and requires less manual debugging.
> I have attached design doc. Huge thanks to [~bharathv] to come up with this
> design at my work place.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
