[
https://issues.apache.org/jira/browse/HBASE-11442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061569#comment-14061569
]
Hudson commented on HBASE-11442:
--------------------------------
SUCCESS: Integrated in HBase-0.98 #400 (See
[https://builds.apache.org/job/HBase-0.98/400/])
HBASE-11442 ReplicationSourceManager doesn't cleanup the queues for recovered
sources (Virag Kothari) (enis: rev ed1a7896e41c88764cd360afaa315f979db9e989)
*
hbase-server/src/test/java/org/apache/hadoop/hbase/replication/regionserver/TestReplicationSourceManager.java
*
hbase-server/src/test/java/org/apache/hadoop/hbase/replication/ReplicationSourceDummy.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSourceManager.java
> 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
> Fix For: 0.99.0, 0.98.4, 2.0.0
>
> 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)
