Re: Failed to process selector key (Connection reset by peer)

Hello! "Connection reset by peer" usually means that remote host went away or in other way could no longer serve the connection. Nothing that we can help. I'm not sure why you're getting an OOM. Maybe you're writing a very large response to some query, which causes remote client to e

Failed to process selector key (Connection reset by peer)

, markedForClose=false]]] 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

Re: Connection reset by peer

t; filterChain=FilterChain[filters=[GridNioCodecFilter > [parser=o.a.i.i.util.nio.GridDirectParser@7419c93, directMode=true], > GridConnectionBytesVerifyFilter], accepted=true]]] > java.io.IOException: Connection reset by peer > at sun.nio.ch.FileDispatcherImpl.read0(Native Method) >

Re: Connection reset by peer

, lastRcvTime=1582246566604, readsPaused=false, filterChain=FilterChain[filters=[GridNioCodecFilter [parser=o.a.i.i.util.nio.GridDirectParser@7419c93, directMode=true], GridConnectionBytesVerifyFilter], accepted=true]]] java.io.IOException: Connection reset by peer

Connection reset by peer

=[GridNioCodecFilter [parser=o.a.i.i.util.nio.GridDirectParser@6b3aff0d, directMode=true], GridConnectionBytesVerifyFilter], accepted=true]]] java.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java

Re: Connection reset by peer

Thank you Ilya, I found that I increased this timeout on server side but not on client side, i guess this should be the problem, it should be the client who closed the connection. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Connection reset by peer

Hello! My recommendation is to increase socketWriteTimeout on TcpCommunicationSpi. It is 2s by default, which is small enough to cause problems under heavy load. Regards, -- Ilya Kasnacheev пт, 7 сент. 2018 г. в 5:48, Justin Ji : > I also encountered this problem before when I am doing

Re: Connection reset by peer

I also encountered this problem before when I am doing performance testing. The reason why I get the exception is the CPU of the client is used 100%, so the connection was closed occasionally. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Connection reset by peer

> we > found that Ignite throws "Connection reset by peer" occasionally after some > complex query, we know it is caused by connection closed while socket > reading/writing, but why it closed? > > can you observe any abnormal info from our log below? > Ignite s

Connection reset by peer

Hi guys, we are using Ignite 2.3.0 we have a Ignite cluster in production which has 4 server nodes, recently we found that Ignite throws "Connection reset by peer" occasionally after some complex query, we know it is caused by connection closed while socket reading/writing, but why