<?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: All Nodes are disconnected from NiFI Cluster in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/All-Nodes-are-disconnected-from-NiFI-Cluster/m-p/187399#M149500</link>
    <description>&lt;P&gt;I should have said that this was using the embedded option for the coordinator. I managed to find the solution by way of an old mailinglist thread (from 2016) [1] that suggested starting the nodes at the same time, rather than one after the other. The reason is that if you start up one node, it will go into a connection frenzy failing to contact the other nodes, quickly hitting the connection limit (and leaving lots of dangling connections in "close wait" state).&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;[1] &lt;A rel="noopener noreferrer noopener noreferrer" href="http://apache-nifi.1125220.n5.nabble.com/Zookeeper-error-td13355.html" target="_blank"&gt;http://apache-nifi.1125220.n5.nabble.com/Zookeeper-error-td13355.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 14 Aug 2019 19:26:12 GMT</pubDate>
    <dc:creator>xalrc</dc:creator>
    <dc:date>2019-08-14T19:26:12Z</dc:date>
  </channel>
</rss>

