ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrey Mashenkov <andrey.mashen...@gmail.com>
Subject Re: stdout - Message queue limit is set to 0, potential OOMEs
Date Wed, 19 Apr 2017 02:14:40 GMT
Hi Sam,

Slow node can cause OOME, as messages for slow node can make queue grows
infinitly.
Also, you can receive messages with higher rate than node able to process,
that also can results in OOME.


On Tue, Apr 18, 2017 at 10:13 PM, javastuff.sam@gmail.com <
javastuff.sam@gmail.com> wrote:

> Recently moved to Ignite 1.9 and noticed below line on stdout -
>
> /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./
>
> Not sure if this existed in older version.
>
> Can anybody explain what does it mean and how to avoid potential OOME?
>
> Thanks,
> -Sam
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/stdout-Message-queue-limit-is-set-to-
> 0-potential-OOMEs-tp12048.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Best regards,
Andrey V. Mashenkov

Mime
View raw message