hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guanghao Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16868) Add a replicate_all flag to avoid misuse the namespaces and table-cfs config of replication peer
Date Thu, 16 Nov 2017 23:53:02 GMT

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

Guanghao Zhang commented on HBASE-16868:

bq. What is the 'misuse' we are trying to avoid?
In our production cluster, there are hundreds of tables. And there are a peer '1' to replicate
all user tables to a peer cluster. If a newbee of hbase create a new table 't1'. Then he want
replicate it to peer cluster and run append_peer_tableCFs '1', {"table1" => []} in hbase
shell. Then we will meet this problem: all other tables will cannot replication to peer cluster!

> Add a replicate_all flag to avoid misuse the namespaces and table-cfs config of replication
> ------------------------------------------------------------------------------------------------
>                 Key: HBASE-16868
>                 URL: https://issues.apache.org/jira/browse/HBASE-16868
>             Project: HBase
>          Issue Type: Improvement
>          Components: Replication
>    Affects Versions: 2.0.0, 3.0.0
>            Reporter: Guanghao Zhang
>            Assignee: Guanghao Zhang
>            Priority: Critical
>             Fix For: 2.0.0-beta-1
>         Attachments: HBASE-16868.master.001.patch, HBASE-16868.master.002.patch, HBASE-16868.master.003.patch,
HBASE-16868.master.004.patch, HBASE-16868.master.005.patch, HBASE-16868.master.006.patch,
HBASE-16868.master.007.patch, HBASE-16868.master.008.patch
> 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

View raw message