hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19492) Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config
Date Wed, 20 Dec 2017 16:29:00 GMT

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

Hudson commented on HBASE-19492:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4260 (See [https://builds.apache.org/job/HBase-Trunk_matrix/4260/])
HBASE-19492 (addendum) Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS (zhangduo: rev cae5c2706b59d6c33c1127b84de88982e3486873)
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/master/replication/ReplicationManager.java


> Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-19492
>                 URL: https://issues.apache.org/jira/browse/HBASE-19492
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Guanghao Zhang
>            Assignee: Guanghao Zhang
>             Fix For: 2.0.0-beta-1
>
>         Attachments: HBASE-19492.master.001.patch, HBASE-19492.master.002.patch, HBASE-19492.master.002.patch,
HBASE-19492.master.002.patch, HBASE-19492.master.003.patch, HBASE-19492.master.004.patch,
HBASE-19492.master.005.patch, HBASE-19492.master.addendum.patch
>
>
> This is a follow-up issue after HBASE-16868. Copied the comments in HBASE-16868.
> This replicate_all flag is useful to avoid misuse of replication peer config. And on
our cluster we have more config: EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS for replication peer.
Let me tell more about our use case. We have two online serve cluster and one offline cluster
for MR/Spark job. For online cluster, all tables will replicate to each other. And not all
tables will replicate to offline cluster, because not all tables need OLAP job. We have hundreds
of tables and if only one table don't need replicate to offline cluster, then you will config
a lot of tables in replication peer config. So we add a new config option is EXCLUDE_TABLECFS.
Then you only need config one table (which don't need replicate) in EXCLUDE_TABLECFS.
> Then when the replicate_all flag is false, you can config NAMESPACE or TABLECFS means
which namespace/tables need replicate to peer cluster. When replicate_all flag is true, you
can config EXCLUDE_NAMESPACE or EXCLUDE_TABLECFS means which namespace/tables can't replicate
to peer cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message