<?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 Joining a node to a NiFi cluster fails because of duplicate node id in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Joining-a-node-to-a-NiFi-cluster-fails-because-of-duplicate/m-p/155414#M32857</link>
    <description>&lt;P&gt;When adding a node to a NiFi cluster, I receive an error saying the NCM prevented connection due to the node id already existing.&lt;/P&gt;</description>
    <pubDate>Fri, 24 Jun 2016 05:04:46 GMT</pubDate>
    <dc:creator>sball</dc:creator>
    <dc:date>2016-06-24T05:04:46Z</dc:date>
    <item>
      <title>Joining a node to a NiFi cluster fails because of duplicate node id</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Joining-a-node-to-a-NiFi-cluster-fails-because-of-duplicate/m-p/155414#M32857</link>
      <description>&lt;P&gt;When adding a node to a NiFi cluster, I receive an error saying the NCM prevented connection due to the node id already existing.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jun 2016 05:04:46 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Joining-a-node-to-a-NiFi-cluster-fails-because-of-duplicate/m-p/155414#M32857</guid>
      <dc:creator>sball</dc:creator>
      <dc:date>2016-06-24T05:04:46Z</dc:date>
    </item>
    <item>
      <title>Re: Joining a node to a NiFi cluster fails because of duplicate node id</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Joining-a-node-to-a-NiFi-cluster-fails-because-of-duplicate/m-p/155415#M32858</link>
      <description>&lt;P&gt;This was resolved by removing the state directory in the node. &lt;/P&gt;&lt;P&gt;The node was originally configured with incorrect hostnames copied from an existing node's nifi.properties, which led the generation of an incorrect nodeid and storage in state. When the host settings were corrected the node id persisted in the state folder. Removing this folder corrected the problem and allowed the node to be joined to the cluster correctly.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jun 2016 05:07:18 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Joining-a-node-to-a-NiFi-cluster-fails-because-of-duplicate/m-p/155415#M32858</guid>
      <dc:creator>sball</dc:creator>
      <dc:date>2016-06-24T05:07:18Z</dc:date>
    </item>
    <item>
      <title>Re: Joining a node to a NiFi cluster fails because of duplicate node id</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Joining-a-node-to-a-NiFi-cluster-fails-because-of-duplicate/m-p/155416#M32859</link>
      <description>&lt;P&gt;Thanks for putting this out Simon!  We definitely need to make this something people don't need to think about.  Ideas welcome.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jun 2016 20:37:36 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Joining-a-node-to-a-NiFi-cluster-fails-because-of-duplicate/m-p/155416#M32859</guid>
      <dc:creator>JoeWitt</dc:creator>
      <dc:date>2016-06-24T20:37:36Z</dc:date>
    </item>
  </channel>
</rss>

