[ 
https://issues.apache.org/jira/browse/HBASE-8844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697376#comment-13697376
 ] 

Patrick commented on HBASE-8844:
--------------------------------

Am I correct in assuming that stop_replication will not harm the master 
cluster, and will only have a negative effect on the backup cluster (leave it 
in an undetermined state)? There's a big difference between data loss on the 
master, and data loss in the standby :)

This may be from lack of familiarity with HBase, but it's not clear to me what 
this means: "start/stop replication is only meant to be used in critical load 
situations". Specifically, I don't know what a critical load situation is. Are 
we talking about server load (as in load average)? If that's the case, is the 
idea to stop replication until load goes down, then start it again?
                
> 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
>            Priority: Minor
>         Attachments: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to