Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Mon, 8 Feb 2016 13:34:39 +0000 (UTC)
From: "Ashish Singhi (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12937494.1454938428000.328137.1454938479956@Atlassian.JIRA>
In-Reply-To: <JIRA.12937494.1454938428000@Atlassian.JIRA>
References: <JIRA.12937494.1454938428000@Atlassian.JIRA>
 <JIRA.12937494.1454938428348@arcas>
Subject: [jira] [Created] (HBASE-15230) ReplicationSource is replicating
 existing WAL data in a newly added peer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Ashish Singhi created HBASE-15230:
-------------------------------------

             Summary: ReplicationSource is replicating existing WAL data in a newly added peer
                 Key: HBASE-15230
                 URL: https://issues.apache.org/jira/browse/HBASE-15230
             Project: HBase
          Issue Type: Bug
            Reporter: Ashish Singhi
            Assignee: Ashish Singhi


Scenario:
1. Add a peer 'p1' and enable table replication for a table 't1'
2. Put some data in the table 't1' and its gets replicated to peer 'p1' as expected.
3. Remove peer 'p1' and truncate the table 't1' in both source and peer cluster.
4. Now add peer 'p2' , there is no data in source cluster in table 't1' but in peer cluster 'p2' where table 't1' already exists, existing WAL data of table 't1' is getting replicated in 'p2'.

Expectation: Table 't1' in peer cluster 'p2' should only have data which is inserted in source cluster table 't1' after adding peer 'p2'


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)