[jira] [Created] (HBASE-24764) Add support of enabling default peer configs via hbase-site.xml for all default replication peers.

["Ankit Jain (Jira)" <ji...@apache.org>]

Ankit Jain created HBASE-24764:
----------------------------------

             Summary: Add support of enabling default peer configs via hbase-site.xml for all default replication peers.
                 Key: HBASE-24764
                 URL: https://issues.apache.org/jira/browse/HBASE-24764
             Project: HBase
          Issue Type: Improvement
            Reporter: Ankit Jain
            Assignee: Ankit Jain


Currently, if a user needs to apply some common peer configs to all the default replication peers, 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 default replication peer configs as part of hbase-site.xml like hbase.replication.peer.default.config="k1=v1;k2=v2.." which can be just applied by a rolling restart. Example below:
<property>
<name>hbase.replication.peer.default.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 default configs in place.

The final peer configuration would be a merge of this default 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)