Hello, I am trying to understand a socket write timeout filling our logs. While the jobs do finish eventually, they are a bit unsettling and would appreciate an explanation. The easy workaround is to seriously bump up the socket write timeout by maximum of affinity task time. However, why is the task time related to the socket timeout? If the task takes too long the socket closes?
The example attached is an affinity call where the callable sleeps for a time longer than the socket write timeout. You will see the client node (TcpCommunicationSpi) closing and recreating the socket. Needlessly (IMHO). Thank you very much for any insights. test.zip <http://apache-ignite-users.70518.x6.nabble.com/file/n6391/test.zip> -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Socket-Closure-due-to-write-timout-tp6391.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
