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/02/12 20:45:00 UTC

[jira] [Created] (IMPALA-6502) Impala Doc: Enabling haproxy for secure impala restricts connection to individual nodes

Alex Rodoni created IMPALA-6502:
-----------------------------------

             Summary: Impala Doc: Enabling haproxy for secure impala restricts connection to individual nodes
                 Key: IMPALA-6502
                 URL: https://issues.apache.org/jira/browse/IMPALA-6502
             Project: IMPALA
          Issue Type: Bug
          Components: Docs
            Reporter: Alex Rodoni
            Assignee: Alex Rodoni


In the following link which describes setting up ha-proxy for impala,
[https://www.cloudera.com/documentation/enterprise/5-2-x/topics/impala_proxy.html#proxy_kerberos]

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.
 
Dylan (AML) encountered this when enabling haproxy for impala. Would definitely be good to call this out as this impacts their user experience...in theory you setup proxy so that all connections go through proxy but they have some users where that is not the case. So a note in our docs would have been helpful to prepare them for that. Thx!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)