[
https://issues.apache.org/jira/browse/HBASE-24765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184915#comment-17184915
]
Duo Zhang commented on HBASE-24765:
-----------------------------------
For me, unless there are security issues or other critical problems, we should
try our best to at least make sure the patch releases can communicate with each
other. Leaving some ugly code on a maintenance release line is also fine if it
is friendly to our users, as we are not likely to introduce new features.
WDYT? Is there any strong reasons here to break the compatibility?
> 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)
