[
https://issues.apache.org/jira/browse/HBASE-24764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Jain updated HBASE-24764:
-------------------------------
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.
was:
<!-- markdown -->
Adds a new configuration parameter "hbase.replication.peer.default.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.
> Add support of adding base peer configs via hbase-site.xml for all
> replication peers.
> -------------------------------------------------------------------------------------
>
> Key: HBASE-24764
> URL: https://issues.apache.org/jira/browse/HBASE-24764
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Affects Versions: 3.0.0-alpha-1, 1.7.0, 2.4.0
> Reporter: Ankit Jain
> Assignee: Ankit Jain
> Priority: Minor
> Fix For: 3.0.0-alpha-1, 1.7.0, 2.4.0
>
> Attachments: HBASE-24764-master.patch
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
