TcpCommunicationSpi warning messages

[kevin <ke...@leonardo.com>]

Hi,

I have a 2 node cluster and I noticed the following warning messages. I
can't see any problems on a superficial level though. The cluster still
looks seemingly stable after these messages. What do the messages mean? Are
they indicative of any problems?

org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi;Communication
SPI Session write timed out (consider increasing 'socketWriteTimeout'
configuration property) [remoteAddr=/xxx, writeTimeout=2000]
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi;Failed to
process selector key (will close): GridSelectorNioSessionImpl
[selectorIdx=1, queueSize=1, writeBuf=java.nio.DirectByteBuffer[pos=0
lim=32768 cap=32768], readBuf=java.nio.DirectByteBuffer[pos=0 lim=32768
cap=32768], recovery=GridNioRecoveryDescriptor [acked=8768, resendCnt=0,
rcvCnt=180725, reserved=true, lastAck=180720, nodeLeft=false,
node=TcpDiscoveryNode [id=3b6bbee2-1170-4ce7-ab6c-a48da1735172,
addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, xxx], sockAddrs=[xxx/xxx,
/0:0:0:0:0:0:0:1%lo:47200, /127.0.0.1:47200, /xxx], discPort=47200, order=1,
intOrder=1, lastExchangeTime=1460390135500, loc=false,
ver=1.5.0#20151229-sha1:f1f8cda2, isClient=false], connected=true,
connectCnt=2, queueLimit=5120], super=GridNioSessionImpl [locAddr=/xxx,
rmtAddr=/xxx, createTime=1460390399220, closeTime=0, bytesSent=92232602,
bytesRcvd=492747831, sndSchedTime=1460390469517, lastSndTime=1460390475504,
lastRcvTime=1460390475504, readsPaused=false,
filterChain=FilterChain[filters=[GridNioCodecFilter
[parser=o.a.i.i.util.nio.GridDirectParser@15573012, directMode=true],
GridConnectionBytesVerifyFilter], accepted=true]]
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi;Closing NIO
session because of unhandled exception [cls=class
o.a.i.i.util.nio.GridNioException, msg=Connection reset by peer]



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/TcpCommunicationSpi-warning-messages-tp4068.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: TcpCommunicationSpi warning messages

[kevin <ke...@leonardo.com>]

Thanks Val. I didn't know that Ignite would resend the message.



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/TcpCommunicationSpi-warning-messages-tp4068p4101.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: TcpCommunicationSpi warning messages

[vkulichenko <va...@gmail.com>]

Hi Kevin,

This message means that one of the messages was not successfully sent within
the timeout. Message is resent in this case and Ignite makes sure that it's
delivered. But if the warnings are frequent, it usually means that the
network is unstable or slow, which can cause performance degradation. In
this case you might consider increasing
TcpCommunicationSpi.socketWriteTimeout.

Makes sense?

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/TcpCommunicationSpi-warning-messages-tp4068p4077.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.