[ https://issues.apache.org/jira/browse/IMPALA-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Brown deleted IMPALA-6502: ---------------------------------- > 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 > Reporter: Alex Rodoni > Assignee: Alex Rodoni > Priority: Major > > 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 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005)