[
https://issues.apache.org/jira/browse/HIVE-18347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16330785#comment-16330785
]
Szehon Ho commented on HIVE-18347:
----------------------------------
After reading the discussion on HIVE-18449, this looks like still a valid
approach as it keeps the randomness of selection, but allows a custom resolver
to resolve the uri. [~thejas] [~vihangk1] Would this patch be ok as is, or is
better to have just the resolver hook, leaving the Consul implementation for
our own repository? (I'm ok with doing the latter)
> Allow dynamic lookup of Hive Metastores via Consul
> --------------------------------------------------
>
> Key: HIVE-18347
> URL: https://issues.apache.org/jira/browse/HIVE-18347
> Project: Hive
> Issue Type: New Feature
> Components: Metastore
> Reporter: Szehon Ho
> Assignee: Szehon Ho
> Priority: Major
> Attachments: HIVE-18347.1.patch, HIVE-18347.2.patch,
> HIVE-18347.3.patch
>
>
> In our organization, we have deployed HiveMetastore and HiveServer2 on Mesos
> as dynamic services for scalability and flexibility.
> In this architecture, we would like to allow HiveServer2 to dynamically load
> balance between Metastores (which may be scaled up and down or to different
> nodes) for different requests.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
