[
https://issues.apache.org/jira/browse/NIFI-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042139#comment-17042139
]
Matt Burgess commented on NIFI-7114:
------------------------------------
Turns out the Data IO Streams weren’t the issue after all, although I think
it’s a good idea to close them explicitly anyway. The real issue is that
DistributedMapCacheClientService only closes the SocketChannel when its close()
method is called, none of the SocketChannelInputStreams. As of
https://github.com/apache/nifi/pull/3658/files , we added an explicit Selector
which also needs to be closed, which is done when the SocketChannelInputStream
is closed. But DistributedMapCacheClientService has never closed it. Updated PR
to come shortly.
> 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
> Assignee: Matt Burgess
> Priority: Major
> Attachments: destination.xml, fifocounts.txt, flow.xml.gz, lsof.log,
> lsof.zip, lsofAfter.log, lsofBefore.log, openFiles.xlsx, reproduction.zip,
> source.xml
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
