[
https://issues.apache.org/jira/browse/NIFI-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431737#comment-15431737
]
Arpit Gupta commented on NIFI-2605:
-----------------------------------
Here is some more detail about the issue.
This issue was seen when a node was disconnected and flow.xml was removed and
node was started back up. After node came back up it had inherited the flow and
then a restart of the whole cluster was issued.
So i think we might have multiple issues here
1. node will always think there is no CC when connecting and will register to
be the CC.
2. node will then ask the current CC for the latest flow and holds it in memory
(but does not save it to disk to immediately). In the above case the node that
was disconnected became the CC and when asked for the latest flow returns the
flow from memory.
3. when starting back up the node that never saved the flow to disk is elected
CC, causing all other nodes to have un-inheritable flows
I think the jira is solving #1. #2 is a new issue and #3 is being resolved as
part of NIFI-1966
> On restart of all nodes in nifi cluster one of the nodes failed to join the
> cluster with fingerprint mismatch
> -------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-2605
> URL: https://issues.apache.org/jira/browse/NIFI-2605
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Arpit Gupta
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.0.0
>
>
> Follow stack trace was present in the node that did not connect
> {code}
> 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
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
