[
https://issues.apache.org/jira/browse/NIFI-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034996#comment-17034996
]
Joe Witt commented on NIFI-7114:
--------------------------------
The most obvious thing growing over time is entries for 'pipe'. Stack overflow
gives us
https://stackoverflow.com/questions/15956452/troubleshooting-too-many-files-open-with-lsof
I then looked at your destination flow and indeed there are many uses of
scripted processors so this is where I'm focusing my review now. Is it that
your scripts are opening handles and not closing them or is that we're not
closing something on their behalf. That is the current investigation.
> 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
> Fix For: 1.11.2
>
> 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)
