You are almost correct. However few things of note: 1) The error messages are unsettling and they do cause a lot of re-transmissions from servers to clients. 2) There was never anything wrong with the socket itself so the error is a bit misleading. Just the jobs taking a long time to execute. There should be nothing wrong with that. 3) I had to increase the queue size as there were queue starvation warnings even if the socket timeout was increased.
Bottom line, I had to greatly bump up the queue size on the tcp provider and everything worked like I expected then and only then. Please keep up the great work. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Socket-Closure-due-to-write-timout-tp6391p6428.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
