[
https://issues.apache.org/jira/browse/NIFI-9725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497897#comment-17497897
]
ASF subversion and git services commented on NIFI-9725:
-------------------------------------------------------
Commit 432f98714fb700b038baf043053f0bf20b8b72bf in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=432f987 ]
NIFI-9725: On shutdown, instead of spawning a background thread to shutdown
Cluster Coordinator, do so in the calling thread. This avoids a race condition
whereby the cluster coordinator cannot be determined because the other thread
has shutdown the FlowController.
This closes #5800
Signed-off-by: David Handermann <[email protected]>
> When shutting down node in cluster, NiFi sometimes fails to notify cluster
> coordinator.
> ---------------------------------------------------------------------------------------
>
> Key: NIFI-9725
> URL: https://issues.apache.org/jira/browse/NIFI-9725
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.16.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When we shutdown a node via {{{}bin/nifi.sh stop{}}}, the node should notify
> the cluster coordinator that it's shutting down. But more often than not, we
> see that the cluster coordinator is not notified, and we see
> ConnectionException's spewed until the heartbeat timeout expires and the
> cluster coordinator marks the node as disconnected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
