[
https://issues.apache.org/jira/browse/HBASE-8844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012492#comment-14012492
]
Jean-Daniel Cryans commented on HBASE-8844:
-------------------------------------------
This part isn't right:
{quote}
It is also cached locally using an AtomicBoolean in the
<i>ReplicationZookeeper</i>
- class. This value can be changed on a live cluster using the
<i>stop_replication</i>
+ class. This value can be changed on a live cluster using the
<i>disable_peer</i>
{quote}
The AtomicBoolean was completely removed, so there's now no way to toggle
hbase.replication while the cluster is running. So that part can be completely
removed, and hbase.replication is now only read when HBase starts.
Regarding disable_peer, it might be good to add that what it does is it stops
sending the edits to that peer cluster, but it still keeps track of all the new
WALs that it will have to replicate when it's re-enabled.
> Document stop_replication danger
> --------------------------------
>
> Key: HBASE-8844
> URL: https://issues.apache.org/jira/browse/HBASE-8844
> Project: HBase
> Issue Type: Task
> Components: documentation
> Reporter: Patrick
> Assignee: Misty Stanley-Jones
> Priority: Minor
> Attachments: HBASE-8844-v2.patch, HBASE-8844.patch
>
>
> The first two tutorials for enabling replication that google gives me [1],
> [2] take very different tones with regard to stop_replication. The HBase docs
> [1] make it sound fine to start and stop replication as desired. The Cloudera
> docs [2] say it may cause data loss.
> Which is true? If data loss is possible, are we talking about data loss in
> the primary cluster, or data loss in the standby cluster (presumably would
> require reinitializing the sync with a new CopyTable).
> [1]
> http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/replication/package-summary.html#requirements
> [2]
> http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/4.2.0/CDH4-Installation-Guide/cdh4ig_topic_20_11.html
--
This message was sent by Atlassian JIRA
(v6.2#6252)
