[NIFI-2605] On restart of all nodes in nifi cluster one of the nodes failed to join the cluster with fingerprint mismatch

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.0.0
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Arpit Gupta
• Created: 19/Aug/16 15:59
• Updated: 24/Aug/16 16:43
• Resolved: 24/Aug/16 16:43

Description

Follow stack trace was present in the node that did not connect

2016-08-18 12:04:55,628 INFO [Process Cluster Protocol Request-1] o.a.n.c.p.impl.SocketProtocolListener Finished processing request ea80ad62-585c-4460-9ee9-93cc12c8db54 (type=NODE_STATUS_CHANGE, length=1052 bytes) from host in 61 millis
2016-08-18 12:04:55,806 ERROR [main] o.a.nifi.controller.StandardFlowService Failed to load flow from cluster due to: org.apache.nifi.controller.UninheritableFlowException: Failed to connect node to cluster because local flow is different than cluster flow.
org.apache.nifi.controller.UninheritableFlowException: Failed to connect node to cluster because local flow is different than cluster flow.
        at org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:866) ~[nifi-framework-core-1.0.0.jar:1.0.0]
        at org.apache.nifi.controller.StandardFlowService.load(StandardFlowService.java:492) ~[nifi-framework-core-1.0.0.jar:1.0.0]
        at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:746) [nifi-jetty-1.0.0.jar:1.0.0]
        at org.apache.nifi.NiFi.<init>(NiFi.java:137) [nifi-runtime-1.0.0.jar:1.0.0]
        at org.apache.nifi.NiFi.main(NiFi.java:227) [nifi-runtime-1.0.0.jar:1.0.0]
Caused by: org.apache.nifi.controller.UninheritableFlowException: Proposed configuration is not inheritable by the flow controller because of flow differences: Found difference in Flows:
Local Fingerprint:   7c84501d-d10c-407c-b9f3-1d80e38fe36a9d7d39c0-0156-1000-ffff-ffffc6ce3a7d9d7d3cd1-0156-1000-0000-0000
Cluster Fingerprint: 9d89d844-0156-1000-e4bc-8ae5e0566749

Edit: As per the discussion below, this manifested due to 3 different problems. The one being solved in this ticket is the one Mark addressed in the linked PR, that a node will always register to be Cluster Coordinator when it joins a cluster.

Issue Links

• links to: GitHub Pull Request #900