[jira] [Resolved] (NIFI-9361) Node can fail to DELETE connection while others finish if upstream component is funnel

["Mark Payne (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-9361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Payne resolved NIFI-9361.
------------------------------
    Resolution: Duplicate

> Node can fail to DELETE connection while others finish if upstream component is funnel
> --------------------------------------------------------------------------------------
>
>                 Key: NIFI-9361
>                 URL: https://issues.apache.org/jira/browse/NIFI-9361
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Priority: Major
>
> When a Connection is deleted, it verifies 3 things before the deletion can occur:
> 1. The queue is empty
> 2. The source either is a Funnel or is stopped
> 3. The destination either is a Funnel or is stopped
> This means that if we delete a connection whose source is a Funnel and whose destination is a Processor, we can have an issue where nodes in the cluster verify that the connection can be deleted.
> Then, when the nodes go to perform the delete, a node can fail to perform the delete because it now has data.
> To avoid this, if the source is a funnel, we need to look at its upstream components (recursively) until we encounter something other than a funnel or we reach a dead end. Only if all upstream components are stopped should we allow the connection to be deleted.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)