You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Guanghao Zhang (Jira)" <ji...@apache.org> on 2020/08/12 06:56:00 UTC
[jira] [Commented] (HBASE-24871) Replication may loss data when
refresh recovered replication sources
[ https://issues.apache.org/jira/browse/HBASE-24871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176074#comment-17176074 ]
Guanghao Zhang commented on HBASE-24871:
----------------------------------------
[~ndimiduk] Take a look about this sir. Should be a blocker for 2.3.1?
> Replication may loss data when refresh recovered replication sources
> --------------------------------------------------------------------
>
> Key: HBASE-24871
> URL: https://issues.apache.org/jira/browse/HBASE-24871
> Project: HBase
> Issue Type: Bug
> Affects Versions: 3.0.0-alpha-1, 2.3.0, 2.2.5
> Reporter: Guanghao Zhang
> Assignee: Sun Xin
> Priority: Major
>
> See code in [https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSourceManager.java#L519]
>
> The WAL enqueued to wrong replication source.
> {code:java}
> for (String queueId : previousQueueIds) {
> ReplicationSourceInterface replicationSource = createSource(queueId, peer);
> this.oldsources.add(replicationSource);
> this.queueStorage.getWALsInQueue(this.server.getServerName(), queueId)
> .forEach(wal -> src.enqueueLog(new Path(wal)));
> toStartup.add(replicationSource);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)