[jira] [Commented] (NIFI-16017) Prevent nodes from (re)joining cluster when it has a Connector in a different Troubleshooting state than Cluster

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-16017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18088669#comment-18088669 ] 

ASF subversion and git services commented on NIFI-16017:
--------------------------------------------------------

Commit a80a072c311571f16d7fc3d1eaccc342ac200424 in nifi's branch refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a80a072c311 ]

NIFI-16017: Do not allow node to Connect to cluster if it has Connector in wrong Troubleshooting state (#11334)

> Prevent nodes from (re)joining cluster when it has a Connector in a different Troubleshooting state than Cluster
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-16017
>                 URL: https://issues.apache.org/jira/browse/NIFI-16017
>             Project: Apache NiFi
>          Issue Type: Task
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> If a node wants to join or rejoin a cluster, but it has a Connector that is in Troubleshooting mode while the cluster is not (or vice versa) the node should be prohibited from joining. This check should happen at the very beginning of the negotiation, just like we do when checking if there would be data loss. This allows us to reject the node without changing any component states, etc.



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