[
https://issues.apache.org/jira/browse/HBASE-26172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-26172:
------------------------------
Description:
Maybe in some environment we still want to use master as registry endpoint, but
this should be controlled at cluster side, not client side.
The implementation of MasterRegistry is almost the same with
RpcConnectionRegistry except that it uses getMasters instead of
getBootstrapNodes to refresh the ‘bootstrap’ nodes connected to. So we could
add configs in server side to control what nodes we want to return to client in
getBootstrapNodes, i.e, master or region server, then the RpcConnectionRegistry
can fully replace the old MasterRegistry. As part of this change, we deprecate
the MasterRegistry.
==== Update ====
We send out an email to mailing list, and there is no objections on not
returning masters as registry endpoints, so here we decide to just deprecated
MasterRegistry.
was:
Maybe in some environment we still want to use master as registry endpoint, but
this should be controlled at cluster side, not client side.
The implementation of MasterRegistry is almost the same with
RpcConnectionRegistry except that it uses getMasters instead of
getBootstrapNodes to refresh the ‘bootstrap’ nodes connected to. So we could
add configs in server side to control what nodes we want to return to client in
getBootstrapNodes, i.e, master or region server, then the RpcConnectionRegistry
can fully replace the old MasterRegistry. As part of this change, we deprecate
the MasterRegistry.
> Deprecate MasterRegistry
> ------------------------
>
> Key: HBASE-26172
> URL: https://issues.apache.org/jira/browse/HBASE-26172
> Project: HBase
> Issue Type: Sub-task
> Components: Client
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
>
> Maybe in some environment we still want to use master as registry endpoint,
> but this should be controlled at cluster side, not client side.
>
> The implementation of MasterRegistry is almost the same with
> RpcConnectionRegistry except that it uses getMasters instead of
> getBootstrapNodes to refresh the ‘bootstrap’ nodes connected to. So we could
> add configs in server side to control what nodes we want to return to client
> in getBootstrapNodes, i.e, master or region server, then the
> RpcConnectionRegistry can fully replace the old MasterRegistry. As part of
> this change, we deprecate the MasterRegistry.
> ==== Update ====
> We send out an email to mailing list, and there is no objections on not
> returning masters as registry endpoints, so here we decide to just deprecated
> MasterRegistry.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
