You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Alex Rodoni (JIRA)" <ji...@apache.org> on 2018/03/06 00:11:00 UTC
[jira] [Closed] (IMPALA-6509) Impala Doc: Enabling haproxy for
secure impala restricts connection to individual nodes
[ https://issues.apache.org/jira/browse/IMPALA-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rodoni closed IMPALA-6509.
-------------------------------
> Impala Doc: Enabling haproxy for secure impala restricts connection to individual nodes
> ---------------------------------------------------------------------------------------
>
> Key: IMPALA-6509
> URL: https://issues.apache.org/jira/browse/IMPALA-6509
> Project: IMPALA
> Issue Type: Task
> Components: Docs
> Affects Versions: Impala 2.10.0
> Reporter: Michael Brown
> Assignee: Alex Rodoni
> Priority: Major
> Fix For: Impala 2.12.0
>
>
> In the following link which describes setting up ha-proxy for impala, in the Special Proxy Considerations for Clusters Using Kerberos section, we need to let users know that after enabling ha-proxy in a kerberized cluster, users can no-longer connect to individual impala daemons directly from impala shell.
> https://impala.apache.org/docs/build/html/topics/impala_proxy.html
> Would definitely be good to call this out as this impacts user experience...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)