slowClientQueueLimit and messageQueueLimit

[Amit Pundir <am...@gmail.com>]

Hello Everyone,

To manage the slow clients, Ignite provides 'slowClientQueueLimit'
configuration on TcpCommunicationSpi.
There is another configuration 'messageQueueLimit'.

Could you please help me understand the difference between the two and
whether - 

1. slowClientQueueLimit is configured on server nodes only, or client nodes
only or on both?
2. messageQueueLimit is configured on server nodes only, or client nodes
only or on both?


Thanks



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/slowClientQueueLimit-and-messageQueueLimit-tp15503.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: slowClientQueueLimit and messageQueueLimit

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

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.