Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/729
@markap14 thanks! have retested tried disconnecting nodes as well as
restarting nodes in cluster. Did see the error logged "This node was elected
Leader for Role 'Cluster Coordinator' but failed to take leadership. Will
relinquish leadership role." on one node with error thrown due to the node not
being part of the cluster. That was also followed up with the logged warning
"Failed to determine which node is elected active Cluster Coordinator:
ZooKeeper reports the address as 127.0.0.1:11001, but there is no node with
this address". This occurred during initial startup and appeared to resolve
once the cluster coodinator (node 2, on port 11001) came online.
I also shutdown node 2 (which was Cluster Coordinator) and noted the
repeated "Failed to send heartbeat due to:
org.apache.nifi.cluster.protocol.ProtocolException: Failed to send message to
Cluster Coordinator due to: java.net.ConnectException: Connection refused"
warning in node 1's log. This was expected based on notes in Jira. Node 1 was
primary node at the time. When node 2 was back online the heartbeat warning no
longer appeared in node 1's log however I could not access node 1's UI (it was
displaying an error demonstrated in the snapshot below).
I've included just the nifi-app logs from both servers since it seemed to
have the most relevant information. Would focus on logs with timestamps
beginning at 13:35 (08-04-2016). Please let me know if you need any additional
information or logs.
<img width="1440" alt="node1-error-cc-restart"
src="https://cloud.githubusercontent.com/assets/1371858/17412342/3f28890a-5a4a-11e6-8ff8-d3acd5a5b0b8.png";>
[logs.zip](https://github.com/apache/nifi/files/402267/logs.zip)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
![https://cloud.githubusercontent.com/assets/1371858/17412342/3f28890a-5a4a-11e6-8ff8-d3acd5a5b0b8.png"](https://cloud.githubusercontent.com/assets/1371858/17412342/3f28890a-5a4a-11e6-8ff8-d3acd5a5b0b8.png"){kind=link}