[
https://issues.apache.org/jira/browse/HBASE-20456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443618#comment-16443618
]
Duo Zhang commented on HBASE-20456:
-----------------------------------
Another way maybe we always create a separated wal group, even if it is not in
A state, the only difference is that we will also write to the remote cluster
when in A state. But it will be hard to deal with peer removal...
And also another places we need to deal with is the LogRoller... It only has a
addWAL method...
> 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
> Reporter: Duo Zhang
> Priority: Major
>
> 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)
