[ https://issues.apache.org/jira/browse/HBASE-20456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449114#comment-16449114 ]
Duo Zhang commented on HBASE-20456: ----------------------------------- Retry. The javac warning is not introduced by this patch. And the failed UTs are not related I suppose. > 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-v3.patch, > HBASE-20456-HBASE-19064-v3.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)