Hello!
I think it involves the following tradeoff:
If you limit it, operations will wait on communication once the limit is
hit.
If you don't limit it, you will see OOM (heap memory) eventually.
This assumes that communication ever becomes a bottleneck, which will
almost never happen.
Since it
Hi ,
We are using 2.8.0 version. And I still get this warning. Can you please
explain the significance of this property and what is the advisable value to
keep in production. I saw someone keep it to 1024. What is the significance
and what happens after 1024.
Thanks,
Prudhvi
--
Sent from:
Hi Rishi,
Yes, but you need set heap size at least 512M and proper off-heap size [1].
But you won't be able to store large amount of data, you will need to enable
persistence, it will allow to extend available memory with dis k[2].
[1]
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
hello igniters,
When I start up the console, I get this warning -
Message queue limit is set to 0 which may lead to potential OOMEs when
running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to message
queues growth on sender and receiver sides.
I am wondering how can I set the
