[
https://issues.apache.org/jira/browse/NIFI-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041408#comment-17041408
]
Paul Kelly commented on NIFI-7114:
----------------------------------
You are correct, running and building this on the same system. Output below.
The only thing non-standard in the sample flow.xml.gz is an
ExecuteGroovyScript, but it's not doing anything fancy. Just getting the flow
file and handing it off to REL_SUCCESS. I included that just to make sure an
ExecuteGroovyScript is running in the sample flow since we use them (with real
scripts, of course) in production.
mvn -version
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /home/xubuntu/Downloads/apache-maven-3.6.3
Java version: 1.8.0_242, vendor: Private Build, runtime:
/usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.3.0-28-generic", arch: "amd64", family: "unix"
java -version
openjdk version "1.8.0_242"
OpenJDK Runtime Environment (build 1.8.0_242-8u242-b08-0ubuntu3~18.04-b08)
OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode)
> 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, 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)