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 2023/03/27 22:45:00 UTC

[jira] [Commented] (NIFI-11333) Disable removing components unless all nodes connected

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

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

Commit d2fdff7b93cb63879b67d5c98932bde6d424c09a in nifi's branch refs/heads/support/nifi-1.x from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d2fdff7b93 ]

NIFI-11333: Do not allow components to be removed while a node is disconnected

This closes #7085

Signed-off-by: David Handermann <ex...@apache.org>


> 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.21.0, 2.latest
>
>          Time Spent: 40m
>  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)