[ 
https://issues.apache.org/jira/browse/NIFI-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041860#comment-17041860
 ] 

Joe Witt commented on NIFI-7114:
--------------------------------

I'm still unable to reproduce any kind of leak here.  In speaking with others 
trying to do the same they are also not finding signs of a leak.

It is of course the case over a period of hours and possibly even longer 
additional file descriptors will be opened and possibly even remain but it 
should definitely level out.  Some flows can have many thousands if not 10s of 
thousands of file descriptors active and this is not necessarily problematic.

The ulimit for open files definitely needs to be changed from the default value 
and we talk about this in the admin guide as I recall.

Happy to keep looking into this as new observations/reproducible 
steps/logs/command output can be shared.  But as of right now this is very 
difficult to replicate.

> 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, fifocounts.txt, flow.xml.gz, lsof.log, 
> lsof.zip, lsofAfter.log, lsofBefore.log, openFiles.xlsx, reproduction.zip, 
> 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)

Reply via email to