[
https://issues.apache.org/jira/browse/NIFI-8384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17311588#comment-17311588
]
Joe Witt commented on NIFI-8384:
--------------------------------
You are definitely leaking sockets.
java XXXXX XXXXX *194u sock 0,7 0t0 29769295
protocol: TCP
java XXXXX XXXXX *195u sock 0,7 0t0 29769296
protocol: TCP
java XXXXX XXXXX *196u sock 0,7 0t0 29769297
protocol: TCP
java XXXXX XXXXX *197u sock 0,7 0t0 29769298
protocol: TCP
java XXXXX XXXXX *198u sock 0,7 0t0 29769299
protocol: TCP
java XXXXX XXXXX *199u sock 0,7 0t0 29769300
protocol: TCP
java XXXXX XXXXX *200u sock 0,7 0t0 29769301
protocol: TCP
java XXXXX XXXXX *201u sock 0,7 0t0 29769302
protocol: TCP
java XXXXX XXXXX *202u sock 0,7 0t0 29769303
protocol: TCP
java XXXXX XXXXX *203u sock 0,7 0t0 29769304
protocol: TCP
java XXXXX XXXXX *204u sock 0,7 0t0 29769305
protocol: TCP
java XXXXX XXXXX *205u sock 0,7 0t0 29769306
protocol: TCP
java XXXXX XXXXX *206u sock 0,7 0t0 29769307
protocol: TCP
java XXXXX XXXXX *207u sock 0,7 0t0 29769308
protocol: TCP
java XXXXX XXXXX *208u sock 0,7 0t0 29769309
protocol: TCP
java XXXXX XXXXX *209u sock 0,7 0t0 29769310
protocol: TCP
java XXXXX XXXXX *210u sock 0,7 0t0 29769311
protocol: TCP
java XXXXX XXXXX *211u sock 0,7 0t0 29769312
protocol: TCP
java XXXXX XXXXX *212u sock 0,7 0t0 29769313
protocol: TCP
java XXXXX XXXXX *213u sock 0,7 0t0 29769314
protocol: TCP
java XXXXX XXXXX *214u sock 0,7 0t0 29769315
protocol: TCP
java XXXXX XXXXX *215u sock 0,7 0t0 29769316
protocol: TCP
java XXXXX XXXXX *216u sock 0,7 0t0 29769317
protocol: TCP
java XXXXX XXXXX *217u sock 0,7 0t0 29769318
protocol: TCP
java XXXXX XXXXX *218u sock 0,7 0t0 29769319
protocol: TCP
java XXXXX XXXXX *219u sock 0,7 0t0 29769320
protocol: TCP
java XXXXX XXXXX *220u sock 0,7 0t0 29769321
protocol: TCP
java XXXXX XXXXX *221u sock 0,7 0t0 29769322
protocol: TCP
java XXXXX XXXXX *222u sock 0,7 0t0 29769323
protocol: TCP
java XXXXX XXXXX *223u sock 0,7 0t0 29769324
protocol: TCP
It is very possible your JVM is doing this. We found something similar
recently and changing the JDK version solved it. Not about nifi at all. It
was Java 8 271 though... If not please try this flow on NIFi 1.13.2 and let us
know.
> NiFi 1.12.1 : Too many open files
> ---------------------------------
>
> Key: NIFI-8384
> URL: https://issues.apache.org/jira/browse/NIFI-8384
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.12.1
> Environment: RHEL 7.8
> java version 1.8.0_281
> Reporter: Roberta
> Priority: Major
> Attachments: lsof_output.zip
>
>
> Hi All,
> Hope everything is fine. I’m writing you as we are experiencing a problem in
> Nifi 1.12.1 on a RHEL 7.8 with java version "1.8.0_281" .
> It is a single node, secured, without any load balancer upstream. However, it
> does have a s2s (it process provenance from another machine), ListSFTP +
> FetchSFTP processors as well as the ExecuteStreamCommand processor.
> After few days running NiFi suddenly shuts down reporting the following
> message:
> INFO [main]org.apache.nifi.bootstrap.Command Apache NiFi is running at PID
> XXXX but is not responding to ping requests
> Looking at the log file we are facing the following WARN:
> WARN [NiFi Web Server-XX-acceptor-X@XXXX
> -ServerConnector@XXXX\{SSL,[ssl,
> http/1.1]}{hostname:9443}]
> o.eclipse.jetty.server.AbstractConnector java.io.IOException: Too many open
> files
> We tried to fix the problem my means of the best practice configurations
> ([https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#configuration-best-practices])
> but the problem persists.
> After some research we found out that a possible cause might be the use of
> the processor FetchSFTP that we use in our flow. It creates always new files
> during SFTP connections (https://issues.apache.org/jira/browse/NIFI-7222). We
> would like to substitute the .nar file you attached to jira but,
> unfortunately, it is no more available.
> Based on your experience, is it possible that the bug found in NiFi 11.1.4
> and 1.12.0 could still be present in the 1.12.1?
> Thank you in advance for your support and let me know if you need further
> details
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
