[HBASE-24764] Add support of adding base peer configs via hbase-site.xml for all replication peers.

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha-1, 1.7.0, 2.4.0
• Fix Version/s: 3.0.0-alpha-1, 1.7.0, 2.4.0
• Component/s: Replication
• Hadoop Flags: Reviewed

Release Note

<!-- markdown -->

Adds a new configuration parameter "hbase.replication.peer.base.config" which accepts a semi-colon separated key=CSV pairs (example: k1=v1;k2=v2_1,v3...). When this configuration is set on the server side, these kv pairs are added to every peer configuration if not already set. Peer specific configuration overrides have precedence over the above default configuration. This is useful in cases when some configuration has to be set for all the peers by default and one does not want to add to every peer definition.

• Assignee: Ankit Jain
• Reporter: Ankit Jain
• Created: 23/Jul/20 19:27
• Updated: 04/Feb/21 07:54
• Resolved: 22/Dec/20 10:07

Description

Today, if a user needs to apply some common base peer configs to all the replication peers on a given cluster, the only way is to execute update_peer_config via CLI which requires manual intervention and can be tedious in case of large deployment fleet.

As part of this JIRA, we plan to add the support to have base replication peer configs as part of hbase-site.xml like hbase.replication.peer.base.config="k1=v1;k2=v2.." which can be easily updated and applied as part of a rolling restart. Example below:
<property>
<name>hbase.replication.peer.base.configs</name>
<value>hbase.replication.source.custom.walentryfilters=x,y,z;hbase.rpc.protection=abc;hbase.xxx.custom_property=123</value>
</property>

This will be empty by default, but one can override to have base configs in place.

The final peer configuration would be a merge of this newly added base config + whatever users override during the peer creation/update (if any).

Related Jira: https://issues.apache.org/jira/browse/HBASE-17543.  HBASE-17543 added the support to add the WALEntryFilters to default endpoint via peer configuration. By this new Jira we are extending the support to update peer configs via hbase-site.xml.

Issue Links

• causes: HBASE-25383 HBase doesn't update and remove the peer config from hbase.replication.source.custom.walentryfilters if the config is already set on the peer.
• links to: GitHub Pull Request #2284
• links to: https://github.com/apache/hbase/pull/2284