[
https://issues.apache.org/jira/browse/KNOX-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742908#comment-14742908
]
ASF subversion and git services commented on KNOX-570:
------------------------------------------------------
Commit 31bb1e029f7a4d89e0f6bb2846e2464babbaa858 in knox's branch
refs/heads/master from [~sumit.gupta]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=31bb1e0 ]
KNOX-570 added zookeeper lookup capability for HS2 HA
> Knox support for HiveServer2 HA
> --------------------------------
>
> Key: KNOX-570
> URL: https://issues.apache.org/jira/browse/KNOX-570
> Project: Apache Knox
> Issue Type: New Feature
> Components: Server
> Affects Versions: 0.7.0
> Reporter: Sumit Gupta
> Assignee: Sumit Gupta
> Fix For: 0.7.0
>
>
> As of Knox 0.5.0, support for WebHDFS HA is available through configuration
> of a HA provider and multiple URLs specified for the WEBHDFS service. There
> is a desire to provide similar support in Knox for HiveServer2 HA.
> HiveServer2 HA has a different implementation than WebHDFS HA in that the
> server information is meant to be looked up via Zookeeper. The configuration
> information involved is typically a Zookeeper ensemble and a Zookeeper
> namespace to lookup the registered HiveServer2 information. The JDBC client
> (Hive) today uses this looked up information to randomly pick a server to
> then send the actual request to. In a failover scenario, the client also
> keeps track of the server that has failed and picks another server at random
> from the list of servers retrieved from Zookeeper. Logic similar to this can
> be implemented in Knox in a specialized Dispatch class so that the client
> connecting to Knox does not have to deal with HA gymnastics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
