You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Andrey Lobachev <pe...@pezzak.ru> on 2019/03/21 20:03:05 UTC
infinite localhost to localhost connections
Hello!
We have Apache ignite cluster v2.7 with Zookeeper discovery. After some
time in the log on each node appeared these messages:
[2019-03-21T22:48:35,536][INFO
][grid-nio-worker-tcp-comm-1-#25][TcpCommunicationSpi] Accepted incoming
communication connection [locAddr=/127.0.0.1:47100, rmtAddr=/127.0.0.1:57186
]
[2019-03-21T22:48:59,119][INFO
][grid-nio-worker-tcp-comm-2-#26][TcpCommunicationSpi] Accepted incoming
communication connection [locAddr=/127.0.0.1:47100, rmtAddr=/127.0.0.1:57188
]
[2019-03-21T22:49:46,173][INFO
][grid-nio-worker-tcp-comm-3-#27][TcpCommunicationSpi] Accepted incoming
communication connection [locAddr=/127.0.0.1:47100, rmtAddr=/127.0.0.1:57194
]
[2019-03-21T22:50:01,658][INFO
][grid-nio-worker-tcp-comm-0-#24][TcpCommunicationSpi] Accepted incoming
communication connection [locAddr=/127.0.0.1:47100, rmtAddr=/127.0.0.1:57200
]
And then:
[2019-03-21T22:50:02,660][ERROR][grid-nio-worker-tcp-comm-0-#24][TcpCommunicationSpi]
Failed to process selector key [ses=GridSelectorNioSessionImpl
[worker=DirectNioClientWorker [super=AbstractNioClientWorker [
idx=0, bytesRcvd=5508546, bytesSent=1747567, bytesRcvd0=0, bytesSent0=18,
select=true, super=GridWorker [name=grid-nio-worker-tcp-comm-0,
igniteInstanceName=null, finished=false, heartbeatTs=1553197801651, hashC
ode=1278667839, interrupted=false,
runner=grid-nio-worker-tcp-comm-0-#24]]],
writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768],
readBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768], inRecover
y=null, outRecovery=null, super=GridNioSessionImpl [locAddr=/
127.0.0.1:47100, rmtAddr=/127.0.0.1:57200, createTime=1553197801651,
closeTime=0, bytesSent=18, bytesRcvd=0, bytesSent0=18, bytesRcvd0=0,
sndSchedTime
=1553197801651, lastSndTime=1553197801651, lastRcvTime=1553197801651,
readsPaused=false, filterChain=FilterChain[filters=[GridNioCodecFilter
[parser=o.a.i.i.util.nio.GridDirectParser@64f568c9, directMode=true],
GridConnectionBytesVerifyFilter], accepted=true, markedForClose=false]]]
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
~[?:1.8.0_191]
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
~[?:1.8.0_191]
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
~[?:1.8.0_191]
at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[?:1.8.0_191]
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
~[?:1.8.0_191]
at
org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:1275)
~[ignite-core-2.7.0.jar:2.7.0]
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2389)
[ignite-core-2.7.0.jar:2.7.0]
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2156)
[ignite-core-2.7.0.jar:2.7.0]
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1797)
[ignite-core-2.7.0.jar:2.7.0]
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
[ignite-core-2.7.0.jar:2.7.0]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_191]
[2019-03-21T22:50:02,661][WARN
][grid-nio-worker-tcp-comm-0-#24][TcpCommunicationSpi] Closing NIO session
because of unhandled exception [cls=class
o.a.i.i.util.nio.GridNioException, msg=Connection reset by peer]
These message persists after restart and even in the case of one node
running in separate zkRootPath. There are some environments with same
configuration which dont have similar behavior. What could it be?
Re: infinite localhost to localhost connections
Posted by Andrey Lobachev <pe...@pezzak.ru>.
I've found. It is our monitoring tool, that checking if tcp port is
listening.
Thanks in advice!
вт, 2 апр. 2019 г. в 16:41, ilya.kasnacheev <il...@gmail.com>:
> Hello!
>
> Does this manifest in any way other than logging?
>
> I guess if some other program would connect to Ignite's communication port
> you will see such messages.
>
> Regards,
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: infinite localhost to localhost connections
Posted by "ilya.kasnacheev" <il...@gmail.com>.
Hello!
Does this manifest in any way other than logging?
I guess if some other program would connect to Ignite's communication port
you will see such messages.
Regards,
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/