[IMPALA-2782] Allow Impala Shell to connect directly to impalad when config with proxy load balancer and kerberos

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Impala 2.2.4
• Fix Version/s: Impala 3.0, Impala 2.12.0
• Component/s: Clients
• Labels: ramp-up shell
• Target Version: Product Backlog
• Assignee: Vincent Tran
• Reporter: Alan Choi
• Created: 17/Dec/15 23:23
• Updated: 19/Feb/19 18:29
• Resolved: 22/Mar/18 03:23

Description

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").

Issue Links

• requires: IMPALA-7130 impala-shell -b / --kerberos_host_fqdn flag overrides value passed in via -i

Sub-Tasks

• Impala 2.12 & 3.0 Docs: Allow Impala Shell to connect directly to impalad when config with proxy load balancer and kerberos: Closed