[
https://issues.apache.org/jira/browse/HBASE-24765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185277#comment-17185277
]
Nick Dimiduk commented on HBASE-24765:
--------------------------------------
bq. 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.
Thanks for pointing this out [~zhangduo]. Patch releases have the most strict
compatibility requirements. I don't want to impose an upgrade process for patch
releases. I think it's very common for operators to roll out service upgrades
without touching applications, and for applications developers to choose
arbitrarily a patch version. For me, the old service needs to work for new
clients, and new service needs to work for old clients. This is not clearly
stated in our book, [~bharathv].
Let's omit this patch from branch-2.3 unless the above level of compatibility
can be provided.
> 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)
