[
https://issues.apache.org/jira/browse/NIFI-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-9442:
-----------------------------
Labels: load-balanced-connections (was: )
> 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
> Labels: load-balanced-connections
> Fix For: 1.16.0
>
> Time Spent: 20m
> 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)
