[
https://issues.apache.org/jira/browse/HBASE-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194458#comment-13194458
]
Lars Hofhansl commented on HBASE-3134:
--------------------------------------
Just so I understand... The difference to {add|remove}Peer is that the
ReplicationSource still keeps track of the logs to be transfered to just
temporarily disables shipment?
Maybe we can show the state via ReplicationZookeeper.listPeers, which is used
by the shell to show all peers.
Personally I like enablePeer() and disablePeer(), because it is entirely clear
what they are doing.
> [replication] Add the ability to enable/disable streams
> -------------------------------------------------------
>
> Key: HBASE-3134
> URL: https://issues.apache.org/jira/browse/HBASE-3134
> Project: HBase
> Issue Type: New Feature
> Components: replication
> Reporter: Jean-Daniel Cryans
> Assignee: Teruyoshi Zenmyo
> Priority: Minor
> Labels: replication
> Fix For: 0.94.0
>
> Attachments: HBASE-3134.patch
>
>
> This jira was initially in the scope of HBASE-2201, but was pushed out since
> it has low value compared to the required effort (and when want to ship
> 0.90.0 rather soonish).
> We need to design a way to enable/disable replication streams in a
> determinate fashion.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
