[
https://issues.apache.org/jira/browse/HBASE-16423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15517308#comment-15517308
]
Hudson commented on HBASE-16423:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-1.4 #428 (See
[https://builds.apache.org/job/HBase-1.4/428/])
HBASE-16423 Add re-compare option to VerifyReplication to avoid (tedyu: rev
b503843bae2b5baa6e5c6ef9dad3395c9caa2e9f)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/replication/VerifyReplication.java
> Add re-compare option to VerifyReplication to avoid occasional inconsistent
> rows
> --------------------------------------------------------------------------------
>
> Key: HBASE-16423
> URL: https://issues.apache.org/jira/browse/HBASE-16423
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Affects Versions: 2.0.0
> Reporter: Jianwei Cui
> Assignee: Jianwei Cui
> Priority: Minor
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-16423-branch-1-v1.patch, HBASE-16423-v1.patch,
> HBASE-16423-v2.patch, HBASE-16423-v3.patch
>
>
> Because replication keeps eventually consistency, VerifyReplication may
> report inconsistent rows if there are data being written to source or peer
> clusters during scanning. These occasionally inconsistent rows will have the
> same data if we do the comparison again after a short period. It is not easy
> to find the really inconsistent rows if VerifyReplication report a large
> number of such occasionally inconsistency. To avoid this case, we can add an
> option to make VerifyReplication read out the inconsistent rows again after
> sleeping a few seconds and re-compare the rows during scanning. This behavior
> follows the eventually consistency of hbase's replication. Suggestions and
> discussions are welcomed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
