[
https://issues.apache.org/jira/browse/HBASE-19293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16257219#comment-16257219
]
Ashish Singhi commented on HBASE-19293:
---------------------------------------
Two comments,
1. It will be good to capture this replicate state in the audit log.
2. Need to update the document section,
http://hbase.apache.org/book.html#hbase.replication.management
> Support add a disabled state replication peer directly
> ------------------------------------------------------
>
> Key: HBASE-19293
> URL: https://issues.apache.org/jira/browse/HBASE-19293
> Project: HBase
> Issue Type: Improvement
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19293.master.001.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
(v6.4.14#64029)
