You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/12/05 11:41:00 UTC

[jira] [Commented] (NIFI-9442) When connection is deleted and source is funnel, should require that components upstream of funnel are stopped

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

ASF subversion and git services commented on NIFI-9442:
-------------------------------------------------------

Commit 2a3f7dafd657a8f1a2d638688889710df3ef8acd in nifi's branch refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2a3f7da ]

NIFI-9442: When deleting a connection, ensure that when the source of the connection is a funnel that its upstream components are checked (recursively)

Signed-off-by: Joe Gresock <jg...@gmail.com>

This closes #5568.


> When connection is deleted and source is funnel, should require that components upstream of funnel are stopped
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-9442
>                 URL: https://issues.apache.org/jira/browse/NIFI-9442
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> This is important for a case in which we have a cluster where two processors (for example) are connected with a funnel in between. In this case, if a user deletes the connection between the funnel and its destination, the web request that is made will be done in two phases: (1) Verify that the request is valid and (2) Delete the connection. But if we don't recursively ensure that the upstream components are stopped, we could have all nodes in the cluster verify the request is valid in the first phase. But before the second phase occurs, one node may now have data within the Connection, so the second phase (the delete) will fail. In that situation, the node's dataflow will differ from the rest of the cluster, and the node will be kicked out of the cluster. To avoid this, we simply ensure that the source is stopped, and if the source is a funnel (which can't be stopped) that its sources are stopped.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)