[jira] [Updated] (HBASE-8844) Document the removal of replication state AKA start/stop_replication

["Jean-Daniel Cryans (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-8844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Daniel Cryans updated HBASE-8844:
--------------------------------------

    Summary: Document the removal of replication state AKA start/stop_replication  (was: Document stop_replication danger)

Updating the jira's summary to better reflect what we ended up doing.

> Document the removal of replication state AKA start/stop_replication
> --------------------------------------------------------------------
>
>                 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-v3-rebased.patch, HBASE-8844-v3.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)