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

Posted to issues@hbase.apache.org by "Appy (JIRA)" <ji...@apache.org> on 2018/02/20 04:18:00 UTC

[jira] [Updated] (HBASE-19293) Support adding a new replication peer in disabled state

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

Appy updated HBASE-19293:
-------------------------
    Summary: Support adding a new replication peer in disabled state  (was: Add  add a disabled state replication peer directly)

> Support adding a new replication peer in disabled state
> -------------------------------------------------------
>
>                 Key: HBASE-19293
>                 URL: https://issues.apache.org/jira/browse/HBASE-19293
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Guanghao Zhang
>            Assignee: Guanghao Zhang
>            Priority: Major
>             Fix For: 3.0.0, 2.0.0-beta-1
>
>         Attachments: HBASE-19293.master.001.patch, HBASE-19293.master.002.patch, HBASE-19293.master.003.patch
>
>
> Now when add a replication peer, the default state is enabled. If you want add a disabled replication peer, you need add a peer first, then disable it. It need two step to finish now.
> Use case for add a disabled replication peer. When user want sync data from a cluster A to a new peer cluster.
> 1. Add a disabled replication peer. And config the table to peer config.
> 2. Take a snapshot of table and export snapshot to peer cluster.
> 3. Restore snapshot in peer cluster.
> 4. Enable the peer and wait all stuck replication log replicated to peer cluster.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)