[
https://issues.apache.org/jira/browse/NIFI-11333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-11333:
------------------------------
Assignee: Mark Payne
Status: Patch Available (was: Open)
> Disable removing components unless all nodes connected
> ------------------------------------------------------
>
> Key: NIFI-11333
> URL: https://issues.apache.org/jira/browse/NIFI-11333
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.latest, 2.latest
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In 1.16 we allows users to start updating flows while nodes are disconnected.
> This has been greatly helpful. However, it can lead to a problem: when a user
> removes a connection and there's data queued on a disconnected node, that
> disconnected node can no longer rejoin the cluster. Instead, it remains
> disconnected; and if the node is shutdown, it cannot be restarted without
> manually changing nifi.properties to change it from a clustered not to a
> standalone node, then restarting, and bleeding the data out, shutting down,
> manually updating properties to make it a clustered node again; and
> restarting.
> This is painful. Instead, we should simply disallow the removal of any
> component unless all nodes in the cluster are connected. Components can still
> be added, started, stopped, and disabled. Just not removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
