[
https://issues.apache.org/jira/browse/HBASE-24765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184872#comment-17184872
]
Bharath Vissapragada commented on HBASE-24765:
----------------------------------------------
Per the compatibility
[guidelines|https://hbase.apache.org/book.html#hbase.versioning] (specifically
section "Client-Server wire protocol compatibility
") which says "We could only allow upgrading the server first. I.e. the server
would be backward compatible to an old client, that way new APIs are OK.", I
thought its okay to ask users to upgrade servers first in a maintenance
release? No?
> 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)
