Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 14 Jul 2014 05:34:04 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12724558.1404163765615.33898.1405316044564@arcas>
In-Reply-To: <JIRA.12724558.1404163765615@arcas>
References: <JIRA.12724558.1404163765615@arcas>
Subject: [jira] [Commented] (HBASE-11442) ReplicationSourceManager doesn't
 cleanup the queues for recovered sources
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Purtell commented on HBASE-11442:
----------------------------------------

Skimmed the patch, +1 for 0.98

> ReplicationSourceManager doesn't cleanup the queues for recovered sources
> -------------------------------------------------------------------------
>
>                 Key: HBASE-11442
>                 URL: https://issues.apache.org/jira/browse/HBASE-11442
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication
>            Reporter: Virag Kothari
>            Assignee: Virag Kothari
>         Attachments: HBASE-11442.patch, HBASE-11442_2.patch
>
>
> Currently, ReplicationSourceManager only cleanups the queues for recovered sources when the queue is being closed. This can cause the already read WAL's files to be read again when a region server doing failover also dies. This can cause replication to possibly happen again
> For e.g lets say RS1 dies with 5 files in queue and RS2 is doing the failover. Now, lets say RS2 dies after going thru 3 files in queue and RS3 is doing the failover. In this case, RS3 will again read those 3 files as they were not removed from the queue. (Though it will read the first file from the set pos. in ZK)


--
This message was sent by Atlassian JIRA
(v6.2#6252)