In a system that is not using native persistence, what is the recommended way of stopping a cluster from running out of memory - or stopping it from crashing when it does?
As per the below jira, memory monitoring appears to be unreliable in the latest version of Ignite: https://issues.apache.org/jira/browse/IGNITE-12096 Even when working, this is an estimate that is updated periodically, which makes it hard to reliably avoid a critical OOM in a system that is rapidly filling caches. It is technically possible to create a custom failure handler - but I understand that trapping the failure in this way is considered to be bad practice, since it can leave Ignite in an inconsistent state. How are people addressing this challenge? Regards, Colin. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
