[
https://issues.apache.org/jira/browse/NIFI-14758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18008862#comment-18008862
]
ASF subversion and git services commented on NIFI-14758:
--------------------------------------------------------
Commit 5a2d42904578080faf94523319750903a36b07e5 in nifi's branch
refs/heads/main from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5a2d429045 ]
NIFI-14758 Wait for new Coordinator when Decommissioning current Coordinator
(#10101)
Signed-off-by: David Handermann <[email protected]>
> 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
> 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)
