Hi Dana, Do you have java.lang.OOM or IgniteOOM ?
if you use TRANSACTIONAL_SNAPSHOT then it's transactional data, page eviction means that you just remove some random pages, so it doesn't make sense to have TRANSACTIONAL_SNAPSHOT mode and remove random data at the same time, it just destroys the whole idea of transactions and data consistency. Might be I miss something about your case, but I would say if you have TRANSACTIONAL_SNAPSHOT you just can not use page eviction, if you can use page eviction, then don't use TRANSACTIONAL_SNAPSHOT. Regarding custom failure handler, it should work, I don't see any reason why it shouldn't, I would really appreciate if you will send us some update about this approach. Thanks, Mike. On Thu, Aug 27, 2020 at 2:13 AM danami <danash...@gmail.com> wrote: > I'd like to extend Colin's question. > > What if I'm using TRANSACTIONAL_SNAPSHOT mode, therefore I can't use Page > Eviction? > How then, other than persistence, can I avoid OOM errors? > Can I write a custom failure handler, to clear the cache/data region for > example? Is it technically possible? (If so, how?) Will it work or is it > bad > and inconsistent as Colin suggested? > Is using persistence my only option to avoid OOM errors or do I have other > choices? > > Thank you for your help, > Dana > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > -- Thanks, Mikhail.
