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

Posted to issues@nifi.apache.org by "Bryan Bende (Jira)" <ji...@apache.org> on 2025/07/17 00:42:00 UTC

[jira] [Created] (NIFI-14758) Decommission of primary node should wait for new primary node

Bryan Bende created NIFI-14758:
----------------------------------

             Summary: Decommission of primary node should wait for new primary node
                 Key: NIFI-14758
                 URL: https://issues.apache.org/jira/browse/NIFI-14758
             Project: Apache NiFi
          Issue Type: Bug
    Affects Versions: 2.4.0
            Reporter: Bryan Bende
            Assignee: Bryan Bende


When decommissioning a node, if the node being decommissioned is the cluster coordinator, there is a period of time where a new coordinator has not been elected yet, in Kubernetes this is the 15 second lease expiration, and if the decommission proceeds through the remaining steps when it removes it self from the cluster, it can result in the new coordinator still having a reference to the decommissioned node.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)