Hi Rishi,
Message queue limit was disabled in 1.9 release because in async mode it may
cause not obvious cluster stall, when OOMEs a quite rare issue. Currently
planned a new back-pressure mechanism [1], another possible issue with
PRIMARY_SYNC was already resolved [2].
Generally it's no need to tune this property, but you always may set it in
TcpCommunicationSpi.setMessageQueueLimit(int).
In Spring xml:
<bean id="grid.cfg.base"
class="org.apache.ignite.configuration.IgniteConfiguration">
<property name="communicationSpi">
<bean
class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
<property name="messageQueueLimit" value="1024"/>
</bean>
</property>
</bean>
[1] https://issues.apache.org/jira/browse/IGNITE-5056
[2] https://issues.apache.org/jira/browse/IGNITE-2466
Thanks!
-Dmitry.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
