<?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: How to achieve load balancing in Nifi 1.1.2 in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-achieve-load-balancing-in-Nifi-1-1-2/m-p/224593#M60778</link>
    <description>&lt;A rel="user" href="https://community.cloudera.com/users/16344/gauravj139.html" nodeid="16344"&gt;@Gaurav Jain&lt;/A&gt;&lt;P&gt;Ideally load-balancing would be handle by the systems pushing data to your NiFI.  When that is not possible and you are forced to ingest all data to a single Node in your NiFi cluster, load-balancing must be handled via a dataflow implementation.&lt;/P&gt;&lt;P&gt;Using a Remote Process Group (RPG) is the most common solution used to redistribute already ingested data across all node sin a cluster, but you can also use multiple PostHTTP processors (1 for every node in your cluster) and a single ListenHTTP processor to build a FlowFile distribution dataflow.&lt;/P&gt;&lt;P&gt;See the following for more info...&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hortonworks.com/articles/16120/how-do-i-distribute-data-across-a-nifi-cluster.html" target="_blank"&gt;https://community.hortonworks.com/articles/16120/how-do-i-distribute-data-across-a-nifi-cluster.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;</description>
    <pubDate>Tue, 09 May 2017 19:36:12 GMT</pubDate>
    <dc:creator>MattWho</dc:creator>
    <dc:date>2017-05-09T19:36:12Z</dc:date>
    <item>
      <title>How to achieve load balancing in Nifi 1.1.2</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-achieve-load-balancing-in-Nifi-1-1-2/m-p/224592#M60777</link>
      <description>&lt;P&gt;Is there is any way to achieve load balancing in Nifi cluster apart from using Remote process group?&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2017 14:33:47 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-achieve-load-balancing-in-Nifi-1-1-2/m-p/224592#M60777</guid>
      <dc:creator>gauravj1391</dc:creator>
      <dc:date>2017-05-09T14:33:47Z</dc:date>
    </item>
    <item>
      <title>Re: How to achieve load balancing in Nifi 1.1.2</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-achieve-load-balancing-in-Nifi-1-1-2/m-p/224593#M60778</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/16344/gauravj139.html" nodeid="16344"&gt;@Gaurav Jain&lt;/A&gt;&lt;P&gt;Ideally load-balancing would be handle by the systems pushing data to your NiFI.  When that is not possible and you are forced to ingest all data to a single Node in your NiFi cluster, load-balancing must be handled via a dataflow implementation.&lt;/P&gt;&lt;P&gt;Using a Remote Process Group (RPG) is the most common solution used to redistribute already ingested data across all node sin a cluster, but you can also use multiple PostHTTP processors (1 for every node in your cluster) and a single ListenHTTP processor to build a FlowFile distribution dataflow.&lt;/P&gt;&lt;P&gt;See the following for more info...&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hortonworks.com/articles/16120/how-do-i-distribute-data-across-a-nifi-cluster.html" target="_blank"&gt;https://community.hortonworks.com/articles/16120/how-do-i-distribute-data-across-a-nifi-cluster.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2017 19:36:12 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-achieve-load-balancing-in-Nifi-1-1-2/m-p/224593#M60778</guid>
      <dc:creator>MattWho</dc:creator>
      <dc:date>2017-05-09T19:36:12Z</dc:date>
    </item>
  </channel>
</rss>

