[
https://issues.apache.org/jira/browse/NIFI-9548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496894#comment-17496894
]
ASF subversion and git services commented on NIFI-9548:
-------------------------------------------------------
Commit 3511ce3d132f18fffd6e2a7aaf14962314d556ef in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3511ce3 ]
NIFI-9548: When disabling RPG transmission, wait for the ports to complete in a
background thread instead of blocking the web thread. Also moved the RPG
initialization logic into flow controller instead of flow service and added a
delay in order to reduce likelihood of ConnectException happening when
pointing to nodes in the same cluster
Signed-off-by: Joe Gresock <[email protected]>
This closes #5641.
> When user disables transmission of Remote Group, web request may block
> indefinitely
> -----------------------------------------------------------------------------------
>
> Key: NIFI-9548
> URL: https://issues.apache.org/jira/browse/NIFI-9548
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.16.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When a user right-clicks on an RPG and clicks Disable Transmission, NiFi
> waits until all threads have stopped before the web thread returns. This can
> cause requests to timeout and result in cluster instability. Instead, we
> should avoid waiting for the threads to complete in the web thread and only
> wait in a background thread. We wait in order to ensure that we set the
> 'transmitting' flag to false when they all complete. But the waiting can be
> done in a background thread.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
