[HBASE-19492] Add EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS support to replication peer config

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0-beta-1, 2.0.0
• Hadoop Flags: Incompatible change, Reviewed

Release Note

Add two new field: EXCLUDE_NAMESPACE and EXCLUDE_TABLECFS to replication peer config.

If replicate_all flag is true, it means all user tables will be replicated to peer cluster. Then allow config exclude namespaces or exclude table-cfs which can't be replicated to peer cluster.

If replicate_all flag is false, it means all user tables can't be replicated to peer cluster. Then allow to config namespaces or table-cfs which will be replicated to peer cluster.

• Assignee: Guanghao Zhang
• Reporter: Guanghao Zhang
• Created: 12/Dec/17 03:18
• Updated: 21/Mar/18 22:20
• Resolved: 20/Dec/17 12:51

Description

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.

Issue Links

• links to: Review Board (master)