hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8844) Document stop_replication danger
Date Tue, 02 Jul 2013 23:41:21 GMT

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

Jean-Daniel Cryans commented on HBASE-8844:

[~plainlystated] I'm talking about removing stop_replication completely, as in nuke it from
space :)

FWIW the doc already talks about disable_peer.
> 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

View raw message