<?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 connection question in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-connection-question/m-p/55467#M62411</link>
    <description>Yes, this is by design. The master roles for Impala preform functions for all Impala daemons, like caching metadata from HMS and HDFS block locations, maintaining a list of available Impala daemons, etc. But they do not manage connections. Each individual Impala daemon will managed the connections made to it and act as the coordinator for those connections.&lt;BR /&gt;&lt;BR /&gt;For production, I recommend putting a load balancer in front of your Impala daemons to spread that connection load across all. Otherwise, having all users connect to a single one will exhaust the memory for that Impala daemon quickly. Another option I have seen is assigning blocks of Impala daemons to specific users groups.</description>
    <pubDate>Tue, 06 Jun 2017 17:50:40 GMT</pubDate>
    <dc:creator>mbigelow</dc:creator>
    <dc:date>2017-06-06T17:50:40Z</dc:date>
    <item>
      <title>Impala connection question</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-connection-question/m-p/55448#M62410</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a hadoop with one mater and two datanode, accessing hdfs can hit the master url, have impala on those two nodes as well, when connect through jdbc i cannot connect with the mater url, have to connect directly through individual node, is this by design or i missed something?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thanks&lt;/P&gt;&lt;P&gt;Shannon&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 11:42:36 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-connection-question/m-p/55448#M62410</guid>
      <dc:creator>ponypony</dc:creator>
      <dc:date>2022-09-16T11:42:36Z</dc:date>
    </item>
    <item>
      <title>Re: Impala connection question</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-connection-question/m-p/55467#M62411</link>
      <description>Yes, this is by design. The master roles for Impala preform functions for all Impala daemons, like caching metadata from HMS and HDFS block locations, maintaining a list of available Impala daemons, etc. But they do not manage connections. Each individual Impala daemon will managed the connections made to it and act as the coordinator for those connections.&lt;BR /&gt;&lt;BR /&gt;For production, I recommend putting a load balancer in front of your Impala daemons to spread that connection load across all. Otherwise, having all users connect to a single one will exhaust the memory for that Impala daemon quickly. Another option I have seen is assigning blocks of Impala daemons to specific users groups.</description>
      <pubDate>Tue, 06 Jun 2017 17:50:40 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-connection-question/m-p/55467#M62411</guid>
      <dc:creator>mbigelow</dc:creator>
      <dc:date>2017-06-06T17:50:40Z</dc:date>
    </item>
    <item>
      <title>Re: Impala connection question</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-connection-question/m-p/55473#M62412</link>
      <description>&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2017 18:50:08 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-connection-question/m-p/55473#M62412</guid>
      <dc:creator>ponypony</dc:creator>
      <dc:date>2017-06-06T18:50:08Z</dc:date>
    </item>
    <item>
      <title>Re: Impala connection question</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-connection-question/m-p/55474#M62413</link>
      <description>&lt;P&gt;A related question, for running impala queries in HUE, i am hitting master, does it randomly hit one of the boxes?&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2017 18:57:04 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-connection-question/m-p/55474#M62413</guid>
      <dc:creator>ponypony</dc:creator>
      <dc:date>2017-06-06T18:57:04Z</dc:date>
    </item>
    <item>
      <title>Re: Impala connection question</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-connection-question/m-p/55482#M62414</link>
      <description>Do you mean that HUE is installed on a master node? The HUE configs will contain an [impala] section and that will contain the Impala Daemon used by HUE. It will only connect to that ImpalaD.</description>
      <pubDate>Tue, 06 Jun 2017 22:15:24 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Impala-connection-question/m-p/55482#M62414</guid>
      <dc:creator>mbigelow</dc:creator>
      <dc:date>2017-06-06T22:15:24Z</dc:date>
    </item>
  </channel>
</rss>

