hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajesh Nishtala (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13416) Recreating a deleted table causes replication of old WALS
Date Tue, 07 Apr 2015 19:45:13 GMT

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

Rajesh Nishtala commented on HBASE-13416:
-----------------------------------------

[~esteban]  after disabling and deleting the table I also remove any peers and readd the peers.
The unit test that can replicate this behavior just landed.  The commit id is d5e81523f719d54e44d24cf6ef8112355aa6281a.
In the setupTablesAndReplication there's a section that rolls wal edits before we delete the
old tables. If this is commented out, and the test is run twice, the second time we can reliably
repro the bug.

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

Mime
View raw message