You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Esteban Gutierrez (JIRA)" <ji...@apache.org> on 2015/04/07 20:26:13 UTC

[jira] [Commented] (HBASE-13416) Recreating a deleted table causes replication of old WALS

    [ https://issues.apache.org/jira/browse/HBASE-13416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14483702#comment-14483702 ] 

Esteban Gutierrez commented on HBASE-13416:
-------------------------------------------

[~rajesh0042] did you delete the replication peer at some point?

> 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)