[
https://issues.apache.org/jira/browse/NIFI-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472335#comment-15472335
]
Mark Payne commented on NIFI-1966:
----------------------------------
Re-opening the ticket, as I have come across an issue. If all nodes in the
cluster have an empty flow, but the flow is different between two of the nodes,
we end up with the following warning in the logs:
2016-09-07 21:23:47,649 WARN [Process Cluster Protocol Request-9]
org.apache.nifi.io.socket.SocketListener Dispatching socket request encountered
exception due to: java.util.NoSuchElementException: No value present
java.util.NoSuchElementException: No value present
at java.util.Optional.get(Optional.java:135) ~[na:1.8.0_101]
at
org.apache.nifi.cluster.coordination.flow.PopularVoteFlowElection.performElection(PopularVoteFlowElection.java:166)
~[nifi-framework-cluster-1.0.0.2.0.0.0-556.jar:1.0.0.2.0.0.0-556]
at
org.apache.nifi.cluster.coordination.flow.PopularVoteFlowElection.isElectionComplete(PopularVoteFlowElection.java:87)
~[nifi-framework-cluster-1.0.0.2.0.0.0-556.jar:1.0.0.2.0.0.0-556]
at
org.apache.nifi.cluster.coordination.flow.PopularVoteFlowElection.castVote(PopularVoteFlowElection.java:118)
~[nifi-framework-cluster-1.0.0.2.0.0.0-556.jar:1.0.0.2.0.0.0-556]
at
org.apache.nifi.cluster.coordination.node.NodeClusterCoordinator.handleConnectionRequest(NodeClusterCoordinator.java:860)
~[nifi-framework-cluster-1.0.0.2.0.0.0-556.jar:1.0.0.2.0.0.0-556]
at
org.apache.nifi.cluster.coordination.node.NodeClusterCoordinator.handle(NodeClusterCoordinator.java:740)
~[nifi-framework-cluster-1.0.0.2.0.0.0-556.jar:1.0.0.2.0.0.0-556]
at
org.apache.nifi.cluster.protocol.impl.SocketProtocolListener.dispatchRequest(SocketProtocolListener.java:167)
~[nifi-framework-cluster-protocol-1.0.0.2.0.0.0-556.jar:1.0.0.2.0.0.0-556]
at
org.apache.nifi.io.socket.SocketListener$2$1.run(SocketListener.java:136)
~[nifi-socket-utils-1.0.0.2.0.0.0-556.jar:1.0.0.2.0.0.0-556]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[na:1.8.0_101]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[na:1.8.0_101]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]
> Address Issue of Nodes Disagreeing About Flow Contents on Startup
> -----------------------------------------------------------------
>
> Key: NIFI-1966
> URL: https://issues.apache.org/jira/browse/NIFI-1966
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Matt Gilman
> Assignee: Mark Payne
> Priority: Blocker
> Labels: migration
> Fix For: 1.1.0
>
>
> During startup a coordinator is selected at random to act as the manager of
> data flow and distributing it to other nodes. This works fine unless that
> selected coordinator happens to have a uninheritable data flow. When this
> occurs, the other nodes either are
> - Able to connect to Coordinator and then unable to join due to an
> uninheritable flow exception due to being presented with a bad data flow. In
> this case, the node shut down.
> - Unable to connect to the Coordinator due to lack of quorem and never
> present with the bad data flow. In this case, the node ran its local flow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
