<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Impala with haproxy and LDAP in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-with-haproxy-and-LDAP/m-p/67112#M77303</link>
    <description>Error visible at the client side is very high level. impala-shell could be used as follows to connect to a particular Impala daemon and test LDAP authentication.

------
impala-shell  -l -u &lt;USER_NAME&gt; --auth_creds_ok_in_clear  -i &lt;PARTICULAR_IMPALA_DAEMON&gt;
------

Reviewing log file of above Impala daemon and a network capture with the LDAP server can reveal integration issues with LDAP server.&lt;/PARTICULAR_IMPALA_DAEMON&gt;&lt;/USER_NAME&gt;</description>
    <pubDate>Wed, 09 May 2018 22:22:59 GMT</pubDate>
    <dc:creator>Suds</dc:creator>
    <dc:date>2018-05-09T22:22:59Z</dc:date>
    <item>
      <title>Impala with haproxy and LDAP</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-with-haproxy-and-LDAP/m-p/66407#M77302</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;
&lt;P&gt;I have configured impala with haproxy for load balancing ,also impala is configured with ldap .&lt;/P&gt;
&lt;P&gt;but i am not able to connect impala using ldap .&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;this is haproxy ==&amp;gt;&amp;nbsp;&lt;SPAN&gt;all&lt;/SPAN&gt;&lt;SPAN&gt;wcc9hddn01.prod.com:21051&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;beeline&amp;gt; !connect "jdbc:hive2://allwcc9hddn01.prod.com:21051/default;user=abcd;password=abcd"&lt;BR /&gt;Connecting to jdbc:hive2://allwcc9hddn01.prod.com:21051/default;user=abcd;password=abcd&lt;BR /&gt;Unexpected end of file when reading from HS2 server. The root cause might be too many concurrent connections. Please ask the administrator to check the number of active connections, and adjust hive.server2.thrift.max.worker.threads if applicable.&lt;BR /&gt;Error: Could not open client transport with JDBC Uri: &lt;SPAN&gt;jdbc:hive2://&lt;/SPAN&gt;&lt;SPAN&gt;all&lt;/SPAN&gt;&lt;SPAN&gt;wcc9hddn01.prod.com:21051/&lt;/SPAN&gt;&lt;SPAN&gt;default&lt;/SPAN&gt;&lt;SPAN&gt;;user=&lt;/SPAN&gt;&lt;SPAN&gt;abcd&lt;/SPAN&gt;&lt;SPAN&gt;;password=&lt;/SPAN&gt;&lt;SPAN&gt;abcd&lt;/SPAN&gt;: null (state=08S01,code=0)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;whereas kerberos works fine . what could be the reason ?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 13:06:35 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-with-haproxy-and-LDAP/m-p/66407#M77302</guid>
      <dc:creator>MSharma</dc:creator>
      <dc:date>2022-09-16T13:06:35Z</dc:date>
    </item>
    <item>
      <title>Re: Impala with haproxy and LDAP</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-with-haproxy-and-LDAP/m-p/67112#M77303</link>
      <description>Error visible at the client side is very high level. impala-shell could be used as follows to connect to a particular Impala daemon and test LDAP authentication.

------
impala-shell  -l -u &lt;USER_NAME&gt; --auth_creds_ok_in_clear  -i &lt;PARTICULAR_IMPALA_DAEMON&gt;
------

Reviewing log file of above Impala daemon and a network capture with the LDAP server can reveal integration issues with LDAP server.&lt;/PARTICULAR_IMPALA_DAEMON&gt;&lt;/USER_NAME&gt;</description>
      <pubDate>Wed, 09 May 2018 22:22:59 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-with-haproxy-and-LDAP/m-p/67112#M77303</guid>
      <dc:creator>Suds</dc:creator>
      <dc:date>2018-05-09T22:22:59Z</dc:date>
    </item>
  </channel>
</rss>

