[
https://issues.apache.org/jira/browse/HBASE-13416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14553667#comment-14553667
]
Dima Spivak commented on HBASE-13416:
-------------------------------------
Not sure if I have more any more context than anyone else, [~esteban] and
[~apurtell]. This JIRA was opened after I reviewed HBASE-13413 and suggested
filing a ticket (this one) and adding a TODO to a workaround that was present
in the newly-created IntegrationTestReplication's code.
> Recreating a deleted table causes replication of old WALS
> ---------------------------------------------------------
>
> Key: HBASE-13416
> URL: https://issues.apache.org/jira/browse/HBASE-13416
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Reporter: Rajesh Nishtala
> Priority: Critical
>
> 1) Create a table and setup replication to another cluster
> 2) Write some data into the source table
> 3) Disable and delete the table from the source cluster and the sink cluster
> 4) Recreate the table with the same schema in the source and sink clusters
> 5) The source cluster is empty but the sink cluster has a copy of the old
> data that is not in the source cluster.
> To work around:
> 1) disable the table in the source cluster
> 2) Roll the WALs across all region servers
> 3) Delete the table in the source cluster
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
