<?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: JDBC Connection String with multiple worker node Impala in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/JDBC-Connection-String-with-multiple-worker-node-Impala/m-p/311837#M224858</link>
    <description>&lt;P&gt;Thanks for your reply&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/31799"&gt;@tusharkathpal&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We already addressed this case with our customer to have the load balancer and vIP. but the customers seeing this is a risk points to expose the worker node IPs to the external departments within the same Organization and needs to be handled internally within the same application ~ department.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any alternative scenarios that can be achieve the same approach without exposing the worker node IPs to external system like F5?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 21 Feb 2021 23:40:08 GMT</pubDate>
    <dc:creator>bb9900m</dc:creator>
    <dc:date>2021-02-21T23:40:08Z</dc:date>
  </channel>
</rss>

