[
https://issues.apache.org/jira/browse/HBASE-20861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538103#comment-16538103
]
Ashish Singhi commented on HBASE-20861:
---------------------------------------
We can use HBASE-9888 for the fix as the solution proposed there I think is
same as what you propose here.
> WAL entries should be replicated which are updated after peer addition
> ----------------------------------------------------------------------
>
> Key: HBASE-20861
> URL: https://issues.apache.org/jira/browse/HBASE-20861
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Reporter: Pankaj Kumar
> Assignee: Pankaj Kumar
> Priority: Major
>
> Steps to reproduce:
> 1. Add a peer
> 2. Enable a table replication
> 3. Put data
> 4. remove peer
> 5. Truncate the table in both the cluster
> 6. Add peer
> Observation:
> Here the old data is getting replicated in the table in peer cluster.
> HBase replication by design upon peer addition always starts replication from
> begining of WAL file, so all replicable wal entries get replicated
> irrespective of peer addition time.
> This can be handled by skipping WAL entries which is having create time
> before peer addition time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
