[
https://issues.apache.org/jira/browse/NIFI-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340113#comment-15340113
]
ASF GitHub Bot commented on NIFI-1900:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/550
NIFI-1900: Verify that connection's destination is not running when t…
…rying to change destination
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markap14/nifi NIFI-1900
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/550.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #550
----
commit 72679a9ca482f1647e819e40193bed477f59cb97
Author: Mark Payne <[email protected]>
Date: 2016-06-20T18:24:33Z
NIFI-1900: Verify that connection's destination is not running when trying
to change destination
----
> 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
>
> *** 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)
