[
https://issues.apache.org/jira/browse/NIFI-14758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-14758:
------------------------------------
Fix Version/s: 2.6.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> 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
> Priority: Major
> Fix For: 2.6.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)
