hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Misty Stanley-Jones (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-8844) Document stop_replication danger
Date Thu, 29 May 2014 01:42:02 GMT

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

Misty Stanley-Jones updated HBASE-8844:

    Attachment: HBASE-8844-v2.patch

I believe this supersedes [~jdcryans] patch and adds info about enabling/disabling/removing
peers. It also adds info about composing the cluster key for the add_peer command. Please
check my work.

> 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

View raw message