Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 18 Oct 2016 04:01:01 +0000 (UTC)
From: "Guanghao Zhang (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13013074.1476763256000.13094.1476763261367@Atlassian.JIRA>
In-Reply-To: <JIRA.13013074.1476763256000@Atlassian.JIRA>
References: <JIRA.13013074.1476763256000@Atlassian.JIRA> <JIRA.13013074.1476763256126@arcas>
Subject: [jira] [Created] (HBASE-16868) Avoid appending table to a peer
 which replicates all tables
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 18 Oct 2016 04:01:03 -0000

Guanghao Zhang created HBASE-16868:
--------------------------------------

             Summary: Avoid appending table to a peer which replicates all tables
                 Key: HBASE-16868
                 URL: https://issues.apache.org/jira/browse/HBASE-16868
             Project: HBase
          Issue Type: New Feature
          Components: Replication
    Affects Versions: 2.0.0
            Reporter: Guanghao Zhang


First add a new peer by shell cmd.
{code}
add_peer '1', CLUSTER_KEY => "server1.cie.com:2181:/hbase".
{code}
If we don't set namespaces and table cfs in peer config. It means replicate all tables to the peer cluster.

Then append a table to the peer config.
{code}
append_peer_tableCFs '1', {"table1" => []}
{code}
Then this peer will only replicate table1 to the peer cluster. It changes to replicate only one table from replicate all tables in the cluster. It is very easy to misuse in production cluster. So we should avoid appending table to a peer which replicates all table.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)