Alessio, It looks like the flow is the not the same on both nodes. Since you only have two nodes, NiFi is not able to come up with a majority of votes. Specifically, it looks like the conf/authorizations.xml or conf/authorizers.xml or conf/users.xml file is out-of-sync. You can try copying these from 1 node to the other, or just deleting them from 1 node and it will inherit the other node's on startup.
Thanks -Mark On Jan 12, 2017, at 8:40 AM, Alessio Palma <alessio.pa...@docomodigital.com<mailto:alessio.pa...@docomodigital.com>> wrote: 2 host secured custer. 2 zookeeper. ________________________________ From: Andre <andre-li...@fucs.org<mailto:andre-li...@fucs.org>> Sent: Thursday, January 12, 2017 2:39:23 PM To: users@nifi.apache.org<mailto:users@nifi.apache.org> Subject: Re: Cluster is still voting on which Flow is the correct flow for the cluster Alessio, May I ask you how many zookeeper form your ensemble? Kind regards On Fri, Jan 13, 2017 at 12:28 AM, Alessio Palma <alessio.pa...@docomodigital.com<mailto:alessio.pa...@docomodigital.com>> wrote: Hello all, there are 5 minutes of negotiation on the cluster which ends in nothing. These are the logs after the handshake fails: host 1 2017-01-12 13:20:36,448 INFO [main] o.a.n.c.c.node.NodeClusterCoordinator Resetting cluster node statuses from {} to {mid1-t029nifi-2.buongiorno.com:8080=NodeConnectionStatus[ nodeId=mid1-t029nifi-2.buongiorno.com:8080<http://mid1-t029nifi-2.buongiorno.com:8080/>, state=DISCONNECTED, Disconnect Code=Not Has Not Yet Connected to Cluster, Disconnect Reason=Not Has Not Yet Connected to Cluster, u pdateId=1], mid1-t029nifi-1.buongiorno.com:8080=NodeConnectionStatus[nodeId=mid1-t029nifi-1.buongiorno.com:8080<http://mid1-t029nifi-1.buongiorno.com:8080/>, state=CONNECTING, updateId=120]} 2017-01-12 13:20:36,450 ERROR [main] o.a.nifi.controller.StandardFlowService Failed to load flow from cluster due to: org.apache.nifi.controller.UninheritableFlowException: Fa iled 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:894) ~[nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.controller.StandardFlowService.load(StandardFlowService.java:493) ~[nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:770) [nifi-jetty-1.1.1.jar:1.1.1] at org.apache.nifi.NiFi.<init>(NiFi.java:156) [nifi-runtime-1.1.1.jar:1.1.1] at org.apache.nifi.NiFi.main(NiFi.java:262) [nifi-runtime-1.1.1.jar:1.1.1] Caused by: org.apache.nifi.controller.UninheritableFlowException: Proposed Authorizer is not inheritable by the flow controller because of Authorizer differences: Proposed Aut horizations do not match current Authorizations at org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:253) ~[nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1461) ~[nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.load(StandardXMLFlowConfigurationDAO.java:83) ~[nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:678) ~[nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:872) ~[nifi-framework-core-1.1.1.jar:1.1.1] ... 4 common frames omitted Host 2 2017-01-12 13:20:36,900 INFO [main] o.a.n.c.c.node.NodeClusterCoordinator Resetting cluster node statuses from {mid1-t029nifi-2.buongiorno.com:8080=NodeConnectionStatus[nodeId=mid1-t029nifi-2.buongiorno.com:8080<http://mid1-t029nifi-2.buongiorno.com:8080/>, state=CONNECTING, updateId=122], mid1-t029nifi-1.buongiorno.com:8080=NodeConnectionStatus[nodeId=mid1-t029nifi-1.buongiorno.com:8080<http://mid1-t029nifi-1.buongiorno.com:8080/>, state=DISCONNECTED, Disconnect Code=Node's Flow did not Match Cluster Flow, Disconnect Reason=org.apache.nifi.controller.UninheritableFlowException: Failed to connect node to cluster because local flow is different than cluster flow., updateId=1]} to {mid1-t029nifi-2.buongiorno.com:8080=NodeConnectionStatus[nodeId=mid1-t029nifi-2.buongiorno.com:8080<http://mid1-t029nifi-2.buongiorno.com:8080/>, state=CONNECTING, updateId=122], mid1-t029nifi-1.buongiorno.com:8080=NodeConnectionStatus[nodeId=mid1-t029nifi-1.buongiorno.com:8080<http://mid1-t029nifi-1.buongiorno.com:8080/>, state=DISCONNECTED, Disconnect Code=Node's Flow did not Match Cluster Flow, Disconnect Reason=org.apache.nifi.controller.UninheritableFlowException: Failed to connect node to cluster because local flow is different than cluster flow., updateId=1]} 2017-01-12 13:20:36,927 INFO [main] o.apache.nifi.controller.FlowController Successfully synchronized controller with proposed flow 2017-01-12 13:20:37,092 INFO [main] org.wali.MinimalLockingWriteAheadLog org.wali.MinimalLockingWriteAheadLog@c42ee90 finished recovering records. Performing Checkpoint to ensure proper state of Partitions before updates What can I check to solve this ?