[
https://issues.apache.org/jira/browse/NIFI-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342654#comment-15342654
]
ASF GitHub Bot commented on NIFI-1900:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/550
Reviewing...
> NiFi allows connections to be moved between processors in cluster when it
> should not
> ------------------------------------------------------------------------------------
>
> Key: NIFI-1900
> URL: https://issues.apache.org/jira/browse/NIFI-1900
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.6.1
> Reporter: Matthew Clarke
> Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> *** The result of this bug is one or more dropped nodes from the NiFi cluster
> requiring flow.xml.gz removal and restart of any dropped nodes.
> Scenario that causes bug:
> 1. NiFi multi-node cluster setup.
> 2. Active flow between two processors.
> 3. Destination processor has actively running threads.
> 4. Stop destination processor.
> 5. Destination processor still has active threads after stop but not on every
> node.
> 6. Drag processor connection to new destination processor.
> 7. Those nodes where the original destination processor did not have active
> threads successfully move connection.
> 8. Those nodes with hung or active threads fail to move connection and are
> then dropped from cluster because of flow no longer matches what is on NCM.
> Recovery requires remove of flow.xml.gz on all dropped nodes and restart of
> those nodes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
