[jira] [Commented] (NIFI-1991) Zero Master Cluster: Modifying a disconnected node causes other nodes to not be able to join cluster

["Mark Payne (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563064#comment-15563064 ] 

Mark Payne commented on NIFI-1991:
----------------------------------

[~andrewmlim] we have not really done anything in 1.1.0 at this time that explicitly was designed to address this issue. However, I think that this has been addressed or greatly mitigated by other features in 1.1.0. Specifically, nodes in a cluster must now vote on which flow is the correct flow (NIFI-1966). The flow won't be available until either enough nodes have joined the cluster or some timeout occurs. This means that if you restart an entire cluster at the same time, you will not be able to modify anything until at least some configurable nodes have connected to the cluster. In addition to this, if you browse to a NiFi instance that has not yet connected to the cluster, you will receive a warning pop-up notifying you that the node is configured to join a cluster but has not yet been able to join.

Do you think this is sufficient, or do you have other ideas that you'd like to see implemented here?

> Zero Master Cluster:  Modifying a disconnected node causes other nodes to not be able to join cluster
> -----------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-1991
>                 URL: https://issues.apache.org/jira/browse/NIFI-1991
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Andrew Lim
>            Priority: Blocker
>             Fix For: 1.1.0
>
>
> I created a zero master cluster with 3 nodes.  All three were up and running.
> I stopped all 3 instances and then brought up just Node1.
> In the Node1 UI, I made some edits to the flow.
> I attempted but was not able to bring up Node2 and Node3 to join the cluster.
> Here is what I saw in the logs:
> 2016-06-09 14:35:47,051 WARN [main] org.apache.nifi.web.server.JettyServer Failed to start web server... shutting down.
> java.lang.Exception: Unable to load flow due to: java.io.IOException: org.apache.nifi.controller.UninheritableFlowException: Failed to connect node to cluster because local flow is different than cluster flow.
>         at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:753) ~[nifi-jetty-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>         at org.apache.nifi.NiFi.<init>(NiFi.java:137) [nifi-runtime-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>         at org.apache.nifi.NiFi.main(NiFi.java:227) [nifi-runtime-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> Caused by: java.io.IOException: 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.load(StandardFlowService.java:501) ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>         at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:744) ~[nifi-jetty-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>         ... 2 common frames omitted
> Caused by: 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:862) ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>         at org.apache.nifi.controller.StandardFlowService.load(StandardFlowService.java:497) ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>         ... 3 common frames omitted
> 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 contains additional configuration from Cluster Fingerprint: eba77dac-32ad-356b-8a82-f669d046aa21eba77dac-32ad-356b-8a82-f669d046aa21org.apache.nifi.processors.standard.LogAttributeNO_VALUEAttributes to IgnoreNO_VALUEAttributes to LogNO_VALUELog prefixNO_VALUEs
>         at org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:219) ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>         at org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1329) ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>         at org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.load(StandardXMLFlowConfigurationDAO.java:75) ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>         at org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:668) ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>         at org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:839) ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
>         ... 4 common frames omitted
> 2016-06-09 14:35:47,052 INFO [Thread-1] org.apache.nifi.NiFi Initiating shutdown of Jetty web server...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)