[
https://issues.apache.org/jira/browse/HBASE-15425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188977#comment-15188977
]
Ashish Singhi commented on HBASE-15425:
---------------------------------------
Thanks all for the comments.
I think same hfile with different seq ids will not cause any impact as in case
of bulk loaded data replication we copy these source hfiles to peer cluster and
then almost run this bulk load tool again, so it will generate a new hfile as
the per seq id in peer cluster. HFiles with different seq ids should also not
impact as the data in both these hfiles are same, so it will not create any
difference.
> Failing to write bulk load event marker in the WAL is ignored
> -------------------------------------------------------------
>
> Key: HBASE-15425
> URL: https://issues.apache.org/jira/browse/HBASE-15425
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.3.0
> Reporter: Ashish Singhi
> Assignee: Ashish Singhi
> Fix For: 2.0.0
>
> Attachments: HBASE-15425.patch, HBASE-15425.v1.patch
>
>
> During LoadIncrementalHFiles process if we fail to write the bulk load event
> marker in the WAL, it is ignored. So this will lead to data mismatch issue in
> source and peer cluster in case of bulk loaded data replication scenario.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
