ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ilya Kasnacheev <ilya.kasnach...@gmail.com>
Subject Re: CacheStore and ignite.close
Date Fri, 17 Aug 2018 10:22:31 GMT
Hello!

It turns out there's some problem with checkpointing-WAL interference.

close(true) cancels current checkpoint, and upon restart some data is
missing from the cache.

We are investigating this.

Regards,

-- 
Ilya Kasnacheev

2018-08-16 10:34 GMT+03:00 Alexey Goncharuk <alexey.goncharuk@gmail.com>:

> Ilya,
>
> Can you please clarify what you mean by 'abandons cache store operations'?
> Does it mean that a read-through/write-through op is omitted, but the
> public API method returns without an error? If it is so, then this is a
> bug. If a public API method finishes with an exception when read-through is
> omitted, then I think it is a correct behavior.
>
> ср, 15 авг. 2018 г. в 16:38, Ilya Kasnacheev <ilya.kasnacheev@gmail.com>:
>
> > Hello!
> >
> > I'm working on https://issues.apache.org/jira/browse/IGNITE-9093 test
> fix
> > Turns out, IgniteDbPutGetWithCacheStoreTest.testReadThrough fails
> > sporadically because the default ignite.close() is close(cancel=true),
> and
> > it seems that it abandons cache store operations. So not all data is
> > read/written from cache store.
> >
> > Is it really so? Is it considered safe?
> >
> > I have a pull request on this topic:
> > https://github.com/apache/ignite/pull/4545
> >
> > Regards,
> >
> > --
> > Ilya Kasnacheev
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message