[ 
https://issues.apache.org/jira/browse/HBASE-26172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Stack 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. So after this change, we could 
deprecate the 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.


> Deprecated MasterRegistry and allow getBootstrapNodes to return master 
> address instead of region server
> -------------------------------------------------------------------------------------------------------
>
>                 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. So after this 
> change, we could deprecate the MasterRegistry.



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

Reply via email to