[
https://issues.apache.org/jira/browse/HIVE-18281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16293397#comment-16293397
]
Prasanth Jayachandran commented on HIVE-18281:
----------------------------------------------
[~asherman] The HA registry in itself is not tied to tez or llap. The actions
taken by the leader can easily be extended for other cases as well,
HiveServer2.java has a listener which handles tez specific session
initialization. Similarly another listener can be added for other engines or
anything non-tez/llap related. The registry client is also generic which
service discovery can make use of to return only the Leader endpoint to client
for connecting (all passive instances does not publish host:port as endpoint).
> HiveServer2 HA for LLAP and Workload Manager
> --------------------------------------------
>
> Key: HIVE-18281
> URL: https://issues.apache.org/jira/browse/HIVE-18281
> Project: Hive
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Prasanth Jayachandran
> Assignee: Prasanth Jayachandran
> Attachments: HIVE-18281.WIP.patch, HSI-HA.pdf
>
>
> When running HS2 with LLAP and Workload Manager, HS2 becomes single point of
> failure as some of the states for workload management and scheduling are
> maintained in-memory.
> The proposal is to support Active/Passive mode of high availability in which,
> all HS2 and tez AMs registers with ZooKeeper and a leader have to be chosen
> which will maintain stateful information. Clients using service discovery
> will always connect to the leader for submitting queries. There will also be
> some responsibilities for the leader, failover handling, tez session
> reconnect etc. Will upload some more detailed information in a separate doc.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
