You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Mark Payne (Jira)" <ji...@apache.org> on 2022/02/25 16:43:00 UTC

[jira] [Created] (NIFI-9729) If a component is stopped while a node is disconnected from cluster, node may not be updated when rejoining

Mark Payne created NIFI-9729:
--------------------------------

             Summary: If a component is stopped while a node is disconnected from cluster, node may not be updated when rejoining
                 Key: NIFI-9729
                 URL: https://issues.apache.org/jira/browse/NIFI-9729
             Project: Apache NiFi
          Issue Type: Bug
          Components: Core Framework
            Reporter: Mark Payne
            Assignee: Mark Payne
             Fix For: 1.16.0


This issue does not affect any already-released version of NiFi. It affects only 1.16.0-SNAPSHOT.

To replicate:
 * Have a running NiFi cluster
 * Start components on the canvas
 * Disconnect a node
 * Stop one of the components
 * Reconnect the node
 * Once the node is reconnected, the component should be stopped (or stopping) but currently will still be running.

The opposite does not appear to be a concern. I.e., if a component was stopped, and changed to running while the node is disconnected, the node will properly update the component state and start running the component upon rejoining the cluster.



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