[
https://issues.apache.org/jira/browse/HBASE-16423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15423444#comment-15423444
]
churro morales commented on HBASE-16423:
----------------------------------------
VerifyReplication has a startTime and endTime parameter. You know your
replication lag from the metrics on the source. So if you are running your
VerifyReplication job and your time is NOW and the max(lag) = x. You can just
set endTime=NOW - x
> 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
> Priority: Minor
>
> 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)
