Hi Denis, Thanks for the analysis.
Today we tried to reduce the Java class path(.../lib/*) when start a server node, but it still sends all the jar files(absolute path) to client. and we also find that, it looks like client node sends its info(path...) to server node, and then server node sends the client's info back to client again... for the TCP window increasing, does Ignite has some attribute that we can configure? or we may need to modify our production system. btw, we are using Ignite 2.3.0. Thanks, Jeff -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
