[
https://issues.apache.org/jira/browse/HBASE-24765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184859#comment-17184859
]
Duo Zhang commented on HBASE-24765:
-----------------------------------
I think this should be something like an incompatible change? We add a new
method for ClientMetaService and the new MasterRegistry.getActiveMaster method
now uses the new method instead of the old getActiveMaster method, which means
a new client with this patch can not communicate with a old server without this
patch.
So for me, I think applying the patch to 2.4.0 is fine, but if we want to apply
to 2.3.x, at least we should change the implementation of getActiveMaster to
make use the old method? Otherwise a new 2.3.x client can not communicate with
a old 2.3.x server.
> Dynamic master discovery
> ------------------------
>
> Key: HBASE-24765
> URL: https://issues.apache.org/jira/browse/HBASE-24765
> Project: HBase
> Issue Type: Sub-task
> Components: Client
> Affects Versions: 3.0.0-alpha-1, 2.3.3, 2.4.0
> Reporter: Bharath Vissapragada
> Assignee: Bharath Vissapragada
> Priority: Major
>
> [~stack]'s idea in the design doc for splittable-meta.
> We can keep a live list of masters to query by fetching the list of available
> masters from any of the available masters configured in the seed list. User
> configured list of masters ("hbase.masters") would be used as a seed list.
> The endpoints are refreshed every 5mins or if any of the registry RPCs hit an
> error (which ever happens first).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
