[
https://issues.apache.org/jira/browse/IMPALA-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Tran resolved IMPALA-2782.
----------------------------------
Resolution: Fixed
Fix Version/s: Impala 2.13.0
> Allow Impala Shell to connect directly to impalad when config with proxy load
> balancer and kerberos
> ---------------------------------------------------------------------------------------------------
>
> Key: IMPALA-2782
> URL: https://issues.apache.org/jira/browse/IMPALA-2782
> Project: IMPALA
> Issue Type: Improvement
> Components: Clients
> Affects Versions: Impala 2.2.4
> Reporter: Alan Choi
> Assignee: Vincent Tran
> Priority: Minor
> Labels: ramp-up, shell
> Fix For: Impala 2.13.0
>
>
> Currently, Impala Shell cannot connect directly to Impalad if it's configured
> with a proxy load balancer and kerberos. In this configuration, Impalad will
> present a credential that uses the load balancer's host. Impala Shell expects
> the impalad host. This mismatch caused the failure.
> It is actually possible for the Impala Shell to expect a different host name
> in the credential. When setting up the SASL connection in sasl_factory(), we
> just need to set the load balancer's host in the sasl_client.setAttr("host").
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
