[
https://issues.apache.org/jira/browse/HBASE-20456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447940#comment-16447940
]
Duo Zhang commented on HBASE-20456:
-----------------------------------
Talked with [~zghaobac] offline, for peer removal we just remove the
ReplicationSource directly so no problem. Let me see if we can do this in the
way described above, i.e, always write wal to a special group, even if it is in
DA or S.
> Support removing a ReplicationSourceShipper for a special wal group
> -------------------------------------------------------------------
>
> Key: HBASE-20456
> URL: https://issues.apache.org/jira/browse/HBASE-20456
> Project: HBase
> Issue Type: Sub-task
> Components: Replication, wal
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: HBASE-19064
>
> Attachments: HBASE-20456-HBASE-19064-v1.patch,
> HBASE-20456-HBASE-19064-v2.patch, HBASE-20456-HBASE-19064.patch
>
>
> For the multi wal implementation, if a new group is created, then we will
> always open a wal writer for it, even if no one uses it later. But for sync
> replication, if the peer is transited to DA or S from A, the special wal will
> be closed and there will be no more wal files for it so we need to close the
> shipper
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
