Mark Payne created NIFI-2333:
--------------------------------
Summary: When a flow consists only of controller-level reporting
tasks/controller services, nodes cannot rejoin cluster once they have
disconnected
Key: NIFI-2333
URL: https://issues.apache.org/jira/browse/NIFI-2333
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework
Affects Versions: 1.0.0
Reporter: Mark Payne
Assignee: Mark Payne
Priority: Blocker
Fix For: 1.0.0
I have a cluster with 3 nodes. If I disconnect and reconnect a node with
nothing in the flow, all works okay. If I add processors to the graph, all
works okay. But if I have no components on the graph but define
controller-level controller services or reporting tasks, then when I disconnect
the node it fails to reconnect when I click 'reconnect'. I end up with the
following stack trace:
2016-07-20 15:19:28,259 ERROR [Reconnect to Cluster]
o.a.nifi.controller.StandardFlowService Handling reconnection request failed
due to: org.apache.nifi.controller.serialization.FlowSynchronizationException:
Failed to connect node to cluster because local flow controller partially
updated. Administrator should disconnect node and review flow for corruption.
org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed
to connect node to cluster because local flow controller partially updated.
Administrator should disconnect node and review flow for corruption.
at
org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:869)
[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.nifi.controller.StandardFlowService.handleReconnectionRequest(StandardFlowService.java:591)
[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.nifi.controller.StandardFlowService.access$300(StandardFlowService.java:97)
[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.nifi.controller.StandardFlowService$2.run(StandardFlowService.java:403)
[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
Caused by:
org.apache.nifi.controller.serialization.FlowSynchronizationException:
java.lang.IllegalStateException: The specified observer identifier already
exists.
at
org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:358)
~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1375)
~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.load(StandardXMLFlowConfigurationDAO.java:81)
~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:670)
[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:841)
[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
... 4 common frames omitted
Caused by: java.lang.IllegalStateException: The specified observer identifier
already exists.
at
org.apache.nifi.logging.repository.StandardLogRepository.addObserver(StandardLogRepository.java:134)
~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.nifi.controller.FlowController.createReportingTask(FlowController.java:2734)
~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.nifi.controller.StandardFlowSynchronizer.addReportingTask(StandardFlowSynchronizer.java:467)
~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:326)
~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
... 8 common frames omitted
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
