[
https://issues.apache.org/jira/browse/HBASE-19293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260320#comment-16260320
]
stack commented on HBASE-19293:
-------------------------------
[~zghaobac] Our Sean is gone till Feb. I think he'd be good w/ your changes
given the explanations. I took a look over the patch. LGTM. On commit fix the
whitespace issues if you don't mind. Needs a release note so others can read
about this nice improvement. Perhaps paste your nice additions to the
replication command on the release note? Thanks.
> 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,
> 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
(v6.4.14#64029)
