You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2018/04/23 07:54:00 UTC

[jira] [Updated] (HBASE-20456) Support removing a ReplicationSourceShipper for a special wal group

     [ https://issues.apache.org/jira/browse/HBASE-20456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Duo Zhang updated HBASE-20456:
------------------------------
         Assignee: Duo Zhang
    Fix Version/s: HBASE-19064
           Status: Patch Available  (was: Open)

> 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.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)