Details
Description
Creating JIRA ticket as requested by exceptionfactory in https://apachenifi.slack.com/archives/C0L9VCD47/p1643633831171269
In NiFi version 1.14.0 and later (https://issues.apache.org/jira/browse/NIFI-8616), the "Idle Connection Expiration" property in PutSplunk is no longer used. This causes quite a bit of warning spam with "Connection reset by peer" in certain configurations:
2022-01-31 16:18:17,268 WARN [PutSplunk[19dc42e1-0b51-340d-a9a6-81ad014d79e1]-41-2] o.a.nifi.processors.splunk.PutSplunk PutSplunk[id=19dc42e1-0b51-340d-a9a6-81ad014d79e1] Communication Failed with Remote Address [/1.2.3.4:12345]: java.io.IOException: Connection reset by peer java.io.IOException: Connection reset by peer at java.base/sun.nio.ch.FileDispatcherImpl.read0(Native Method) at java.base/sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) at java.base/sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:276) at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:233) at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:223) at java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:356) at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:253) at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132) at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:350) at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:151) at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:719) at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:655) at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:581) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493) at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986) at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) at java.base/java.lang.Thread.run(Thread.java:829)
One example where this causes this problem is when using an LB between NiFi and Splunk.
Attachments
Issue Links
- relates to
-
NIFI-8616 Migrate SSL socket code to use Netty
- Resolved
- links to