<?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: Zombie Nodes; Disconnected State but can't delete in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Zombie-Nodes-Disconnected-State-but-can-t-delete/m-p/315152#M226366</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Update for those playing along at home:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;What appears to be happening is when a zombie node is disconnected via a heartbeat fail, and it cant be deleted, is that the cluster coordinator for whatever reason is still trying to talk to it about the delete. I've&amp;nbsp;&lt;/SPAN&gt;tricked&lt;SPAN&gt;&amp;nbsp;it into working by adding the hostname to the coordinators&amp;nbsp;&lt;/SPAN&gt;/etc/hosts&lt;SPAN&gt;&amp;nbsp;and pointing to itself (the coordinator) ... its clear that this is not the desired/anticipated path, but its unclear&amp;nbsp;&lt;/SPAN&gt;&lt;I&gt;why&lt;/I&gt;&lt;SPAN&gt;&amp;nbsp;this is happening and if it is something in how we've configured this. Cluster joins are just done via Nifi internals (we dont do anything different) .. the only thing we are doing here is forcibly&amp;nbsp;knocking over the node so it goes unhealthy in the cluster and is flagged as disconnected&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 23 Apr 2021 13:49:14 GMT</pubDate>
    <dc:creator>cgmckeever</dc:creator>
    <dc:date>2021-04-23T13:49:14Z</dc:date>
  </channel>
</rss>

