nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <>
Subject [jira] [Commented] (NIFI-6569) Site-to-Site not timing out when reading from remote NiFi
Date Mon, 02 Sep 2019 02:52:00 GMT


ASF subversion and git services commented on NIFI-6569:

Commit 9ba280680ff8b40b15d460e6f822c2b10d4373c3 in nifi's branch refs/heads/master from Mark
[;h=9ba2806 ]

NIFI-6569, NIFI-6570: Fixed bug that caused read timeouts not to occur with site-to-site.
Fixed bug that caused site-to-site listener not to accept connections if there are no input/output
ports on the root group - this used to be a valid check and was done to prevent spawning extra
threads and doing extra work if no ports exist but now that we have site-to-site ports outside
of the root group it's no longer a reasonable condition to check.

This closes #3658.

Signed-off-by: Koji Kawamura <>

> Site-to-Site not timing out when reading from remote NiFi
> ---------------------------------------------------------
>                 Key: NIFI-6569
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.10.0
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
> I created two simple flows:
> Remote Input Port -> LogAttribute
> GenerateFlowFile -> RemoteProcessGroup (pointing to self)
> So that I can simply feed generated FlowFiles to the RPG to the LogAttribute. When I
ran this using Java 11, the listener failed to start (known issue, NIFI-5952). However, what
I noticed is that the RPG would not stop when I clicked Disable Transmission. Instead, the
web request to disable would hang. Thread dumps show the call to try to find out which nodes
are in the cluster are never timing out. This seems to be related to NIFI-4461, though it's
not entirely clear at this point.

This message was sent by Atlassian Jira

View raw message