[
https://issues.apache.org/jira/browse/HIVE-18449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16329668#comment-16329668
]
Sahil Takiar commented on HIVE-18449:
-------------------------------------
[~thejas] the use case relates to how a standalone HMS service is deployed in
High Availability mode. When multiple standalone HMS instances are deployed,
one simple way to configure them in a active-passive HA mode is to have clients
connect to the first URI in {{hive.metastore.uris}}. If the first URI in the
list fails, then all connections are transferred to the second URI in the list.
Alternatively, if a user wants a active-active HA deployment then the HMS
client would randomly pick a URI from the URIS list. Allowing for a
configurable policy enables users to pick between an active-active vs. a
active-passive HA configuration.
[~szehon] I briefly took a look at HIVE-18347, it looks very similar to what I
had in mind here, although slightly different. It looks like your change allows
for a pluggable way to resolve a given URI, but still uses the "random" policy
for picking a URI from a set of URIs. I think they could be potentially
combined, or if you plan on merging HIVE-18347 soon we can build upon it here.
> Add configurable policy for choosing the HMS URI from hive.metastore.uris
> -------------------------------------------------------------------------
>
> Key: HIVE-18449
> URL: https://issues.apache.org/jira/browse/HIVE-18449
> Project: Hive
> Issue Type: Improvement
> Components: Metastore
> Reporter: Sahil Takiar
> Assignee: Janaki Lahorani
> Priority: Major
>
> HIVE-10815 added logic to randomly choose a HMS URI from
> {{hive.metastore.uris}}. It would be nice if there was a configurable policy
> that determined how a URI is chosen from this list - e.g. one option can be
> to randomly pick a URI, another option can be to choose the first URI in the
> list (which was the behavior prior to HIVE-10815).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
