This appears to be a problem that is fixed in Ignite 2.7.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
We were using Ignite 2.4 (update pending). Ignite 2.5 and later seens to
treat OOM as a critical error by default and stops the node. The reproducer
below uses a failure handler to stop this from happening. It allocates a
100MB (configurable - 100MB is quite small) region and fills it up with
data.
What ignite version do you use? Could you please share a reproducer with us?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Ignite DataRegionMetrics reports that memory *is* freed up when removing
items from the cache. However, Ignite continues to throw an OOM exception on
each subsequent cache removal. Cache puts are unsuccessful.
So although Ignite reports that the memory is free, it doesn't seem possible
to actually
I wrote a test for what happens in the case that a DataRegion runs out of
memory. I filled up a cache with records until I received the expected
IgniteOutOfMemoryException. Then I tried to remove entries from the cache -
expecting that memory would be freed up again.
What I found is that any cache
