[
https://issues.apache.org/jira/browse/NIFI-14795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18010509#comment-18010509
]
ASF subversion and git services commented on NIFI-14795:
--------------------------------------------------------
Commit 4707a446a4ff4bb8ddd34e84d23c4c3b62266a0d in nifi's branch
refs/heads/main from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=4707a446a4 ]
NIFI-14795 Restore use of getConnectionStatus in ClusterDecommissionTask
Signed-off-by: Pierre Villard <[email protected]>
This closes #10142.
> Decommission of a node stuck waiting for state change
> -----------------------------------------------------
>
> Key: NIFI-14795
> URL: https://issues.apache.org/jira/browse/NIFI-14795
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.5.0
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In NIFI-14758 we introduced `fetchConnectionStatus` for use from the
> `cluster-status` command, but we also switched the internal calls in the
> decommission task to use this new method, instead of getConnectionStatus.
> This has caused an issue where a node can get stuck during decommission
> waiting to see a specific state from `fetchConnectionStatus` that it never
> sees. We should switch these calls back to `getConnectionStatus` which uses
> the current node's local view of the node's state.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
