messageQueueLimit provides back pressure. If there are too many outbound pending messages in the queue, sender will wait until at least one of the messages is sent.
slowClientQueueLimit is the maximum amount of outbound messages to a client node before that client is kicked out from topology. This is done to make sure slow clients do not cause overall degradation. Configuration for TcpCommunicationSpi is typically the same on all nodes, including servers and clients. I don't see a reason to have different values on different nodes. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/slowClientQueueLimit-and-messageQueueLimit-tp15503p15522.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
