[
https://issues.apache.org/jira/browse/NIFI-7200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17056109#comment-17056109
]
Mark Payne commented on NIFI-7200:
----------------------------------
It looks like this issue was introduced in NIFI-6530. Additionally, NIFI-6530
introduced another bug in the way that the load balancing/distribution with
site-to-site worked. As a result, if all data is queued up in one node, the
data will never get pulled. It will just sit, queued up, until another node has
data. At that point, the data may or may not be pulled from the first node.
Because NIFI-6530 was intended to be a performance improvement, I submitted a
PR that simply reverts the commit. Such a performance improvement can be looked
at again, if necessary.
> IPv4 socket resource leak
> -------------------------
>
> Key: NIFI-7200
> URL: https://issues.apache.org/jira/browse/NIFI-7200
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Joe Witt
> Priority: Critical
> Fix For: 1.12.0, 1.11.4
>
> Attachments: Screen Shot 2020-03-06 at 1.04.57 PM.png, lsof
> test-node2.txt, test-node1-flow.png, test-node1.dump, test-node1.logs.zip,
> test-node2-flow.png, test-node2.dump, test-node2.logs.zip
>
>
> https://issues.apache.org/jira/browse/NIFI-7114?focusedCommentId=17044888&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17044888
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
