[
https://issues.apache.org/jira/browse/NIFI-7200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053658#comment-17053658
]
Richard St. John commented on NIFI-7200:
----------------------------------------
[~joewitt] Sorry for the lack of details, but it has been difficult identifying
anything related to this rather convoluted issue. On the upside, we have found
a work-around for our use-case.
Our use-case goes something like this: One 4-node, secure NiFi cluster
(cluster A) sending data to and receiving data from a remote 6-node, secure
NiFi cluster (cluster B) via a remote process group residing on cluster A. To
be clear, cluster B houses both the remote input port and the remote output
port. This means that cluster A has a relationship connected to the remote
process group and a relationship from the remote process group. !Screen Shot
2020-03-06 at 1.04.57 PM.png!
We found a work around that isolates the issue around this remote process
group. Cluster B had both the remote input port and the remote output port.
We replaced the remote output port on cluster B with a *remote process group*
and added a remote input port on cluster A. Now the lsof count has stabilized.
We use Amazon Linux 2 AMIs
I hope this is useful
> 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
> Attachments: Screen Shot 2020-03-06 at 1.04.57 PM.png
>
>
> 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)
