[
https://issues.apache.org/jira/browse/NIFI-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037201#comment-17037201
]
Joe Witt commented on NIFI-7114:
--------------------------------
Fair enough. What you're referring to though is likely something unrelated
also leading to file leakage. From the one reporter that has provided concrete
data there is no presence of CLOSE_WAIT sockets at all. Just the pipes.
What kind of S2S connections do you have? (RAW/HTTP) . Do they use TLS? CLOSE
WAIT *should* mean that the client closed the connection but that our code
hasn't called close. So this should be relatively easy to find but we need
details and ideally log information.
> NiFi not closing file handles
> -----------------------------
>
> Key: NIFI-7114
> URL: https://issues.apache.org/jira/browse/NIFI-7114
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 1.10.0, 1.11.0
> Environment: Amazon EC2 running either Amazon Linux 2 or Ubuntu 18.04.
> NiFi has been installed with no change to any configuration file.
> Reporter: Vinicius Zolin
> Priority: Major
> Attachments: destination.xml, lsof.log, lsof.zip, lsofAfter.log,
> lsofBefore.log, openFiles.xlsx, source.xml
>
>
> Since at least version 1.10 NiFi stopped closing file handles. It opens circa
> 500 files per hour (measured using lsof) without any apparent limit until it
> crashes due to too many open files.
>
> Increasing the computer open file limit is not a solution since NiFi will
> still crash, it'll only take longer to do so.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
