Re: Ignite 2.5 | Can't restore memory - critical part of WAL archive is missing with walMode=NONE

Hi Andrey, Thanks for your time. Regards, --- Emmanuel. On 08/06/18 16:42, Andrey Mashenkov wrote: Hi Emmanuel, Sorry for late answer. I've found I check your test against master branch and test passes, but it fails on 2.5 branch. It looks like already fixed. On Wed, Jun 6, 2018 at 3:47 PM

Re: Ignite 2.5 | Can't restore memory - critical part of WAL archive is missing with walMode=NONE

Hi Emmanuel, Sorry for late answer. I've found I check your test against master branch and test passes, but it fails on 2.5 branch. It looks like already fixed. On Wed, Jun 6, 2018 at 3:47 PM, Emmanuel Marchand < emmanuel.march...@exensa.com> wrote: > I was wrong on the introduction of the excep

Re: Ignite 2.5 | Can't restore memory - critical part of WAL archive is missing with walMode=NONE

I was wrong on the introduction of the exception. I guess it was added by a fix about IGNITE-8066 . Regards, --- Emmanuel. On 05/06/18 11:05, Emmanuel Marchand wrote: Hi,

Re: Ignite 2.5 | Can't restore memory - critical part of WAL archive is missing with walMode=NONE

Hi, Here are some more informations : * the region are as in the provided configuration file. I guess there is only one. * I have 3 caches and I update all 3 using one datastreamer with custom receiver for each. * all caches are not using any backup and atomicity mode is set to ATOMIC

Re: Ignite 2.5 | Can't restore memory - critical part of WAL archive is missing with walMode=NONE

Hi, I've make a simple test and still can't reproduce this. Would you please take a look if I missed smth? Is it possible you have more than one region and\or cache? On Tue, Jun 5, 2018 at 5:41 PM, Emmanuel Marchand < emmanuel.march...@exensa.com> wrote: > Hi, > > I'm not sure I can provide a

Re: Ignite 2.5 | Can't restore memory - critical part of WAL archive is missing with walMode=NONE

Hi, I'm not sure I can provide a reproducer, but here is some informations : * configuration file attached * 2 server nodes, 1 client (+ visor) * I'm streaming enough data to trigger a checkpoint with a reason 'too many dirty pages' o [INFO][db-checkpoint-thread-#69][GridCacheDatabase

Re: Ignite 2.5 | Can't restore memory - critical part of WAL archive is missing with walMode=NONE

Hi, I can't reproduce the issue. Is it possible grid configuration was changed between runs? Is it possible to share a reproducer? On Tue, Jun 5, 2018 at 12:05 PM, Emmanuel Marchand < emmanuel.march...@exensa.com> wrote: > Hi, > > I'm testing v2.5 vs v2.4 for persisted dataregion with *walModel

Ignite 2.5 | Can't restore memory - critical part of WAL archive is missing with walMode=NONE

Hi, I'm testing v2.5 vs v2.4 for persisted dataregion with *walModel = NONE* and while performance seems better I failed to restart the cluster after what I think is a proper shutdown (using top -deactivate then kill -k from visor). When I try to reactivate the cluster (using top -activate f