Thanks for the response. When killing a non-coordinator node, it does take 8 * 5 seconds before I see this :
nifi-app.log:2017-05-18 12:04:29,644 INFO [Heartbeat Monitor Thread-1] o.a.n.c.c.node.NodeClusterCoordinator Status of centos-b:8080 changed from NodeConnectionStatus[nodeId=centos-b:8080, state=CONNECTED, updateId=26] to NodeConnectionStatus[nodeId=centos-b:8080, state=DISCONNECTED, Disconnect Code=Lack of Heartbeat, Disconnect Reason=Have not received a heartbeat from node in 43 seconds, updateId=27] When killing the coordinator node, the newly appointed coordinator doesn't seem to detect the heartbeat timeout. I'll see if I can enable the debug logging. My Nifi runs inside a KVM. KVM includes 3 seperate VMs. External zookeeper (replicated mode) running on the 3 VMs, and 2 VMs used for NiFi nodes. I have the same issue in a dockerized environment -- View this message in context: http://apache-nifi-users-list.2361937.n4.nabble.com/Nifi-Cluster-fails-to-disconnect-node-when-node-was-killed-tp1942p1948.html Sent from the Apache NiFi Users List mailing list archive at Nabble.com.
