Re: Ignite Expiry Inconsistency with Native Persistence

Thank you very much Val!! Will keep an eye on when it get resolved. On Thu, Mar 22, 2018 at 8:24 PM vkulichenko wrote: > Subash, > > Yes, I reproduced it now. Looks like a bug to me, I created a ticket: > https://issues.apache.org/jira/browse/IGNITE-8027 > > -Val

Re: Ignite Expiry Inconsistency with Native Persistence

Subash, Yes, I reproduced it now. Looks like a bug to me, I created a ticket: https://issues.apache.org/jira/browse/IGNITE-8027 -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Expiry Inconsistency with Native Persistence

I tried with proper ignite.stopAll() and it worked as expected!! So with a node crash, those expiration related metadata not got persisted. Is there a time for it to write and flush to disk ? On Wed, Mar 21, 2018 at 12:55 AM Subash Chaturanga wrote: > Hi Val, > Only one

Re: Ignite Expiry Inconsistency with Native Persistence

Hi Val, Only one node running. And at step 2 when you say, wait for output and stop, did you mean Ignite.stop() or kill -9 jvm. What I do is kill -9. On Tue, Mar 20, 2018 at 9:21 PM vkulichenko wrote: > Subash, > > When you run the test, is this the only node, or

Re: Ignite Expiry Inconsistency with Native Persistence

Subash, When you run the test, is this the only node, or there are some other nodes running? I actually can't reproduce the issue even with your code. Here is what I do: - Clean up the work directory. - Run the test, wait for output, stop. - Comment out 'put' invocations. - Run again. The output

Re: Ignite Expiry Inconsistency with Native Persistence

If you can send me the working code I can try to compare what’s missing. On Thu, Mar 15, 2018 at 10:14 AM Subash Chaturanga wrote: > Here’s my code. > > *public static void *main(String[] args) *throws*InterruptedException { > > String region = *"4GRegion"*; >

Re: Ignite Expiry Inconsistency with Native Persistence

Here’s my code. *public static void *main(String[] args) *throws*InterruptedException { String region = *"4GRegion"*; String cacheName = *"bar2"*; String path = *"C:**\\**dev**\\**dpsrc**\\**simple-java**\\**work"*; DataStorageConfiguration storageCfg = *new*

Re: Ignite Expiry Inconsistency with Native Persistence

Subash, This is weird, I'm doing exactly the same and not able to reproduce the issue. Can you share your whole test so that I can run it as-is? -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Expiry Inconsistency with Native Persistence

Hi Val, I am using ignite 2.3 Have a simple java Main method that has following 1. dataStorageConfig.set(dataRegionConfig) 2. ignitconfig.setDataStorageConfig(dataStorageConfig) 3. IgniteConfig.setDiscoverySpi(spi) 4.Ignition.start(igniteConfig) 5. CacheConfiguration cc =

Re: Ignite Expiry Inconsistency with Native Persistence

I was actually not correct here. Although there are some known issues, expiration is supposed to work with both memory and persistence. Subash, can you provide more details on how you reproduce the issue? I'm getting null even after I restart the node. Are you doing anything else there? -Val

Re: Ignite Expiry Inconsistency with Native Persistence

Thank you for explanation. Currently Ignite does not have any settings which allow to limit used disk space in persistent storage. вт, 13 мар. 2018 г. в 21:06, Subash Chaturanga : > I mean, for example; we provide max value 500MB for durable memory under > eviction policy,

Re: Ignite Expiry Inconsistency with Native Persistence

I mean, for example; we provide max value 500MB for durable memory under eviction policy, that will make sure Ignite will only use 500MB from the RAM no matter what. When native persistence comes into the picture, Ignite store entries in disk. So if we run on production, we want to make sure we

Re: Ignite Expiry Inconsistency with Native Persistence

Hi, I'm not sure I understand what high watermark for persistence mean. Could you please explain? пн, 12 мар. 2018 г. в 19:43, Subash Chaturanga : > Thank you very much for the responses. > > Will keep an eye on when it will be released. Any estimated release for > the fix ?

Re: Ignite Expiry Inconsistency with Native Persistence

Thank you very much for the responses. Will keep an eye on when it will be released. Any estimated release for the fix ? One more question I asked was, can we provide a high watermark for persistence store ? On Mon, Mar 12, 2018 at 12:24 PM vkulichenko wrote: >

Re: Ignite Expiry Inconsistency with Native Persistence

Currently expired entry is removed only from memory. The same will be supported for persistence layer after this ticket is implemented: https://issues.apache.org/jira/browse/IGNITE-5874. -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Expiry Inconsistency with Native Persistence

Hi, It seems this is very similar with https://issues.apache.org/jira/browse/IGNITE-6964 After node restart there can be some delay in removal. When some other entry will be removed, entry which survived during restart should be removed also. I guess entry may come from WAL after restart and

Re: Ignite Expiry Inconsistency with Native Persistence

Ideally 3 nodes. So expiry inconsistency is a known issue ? But I reproduce the expiry inconsistency issue even in a single node with the steps mentioned earlier. We are evaluating Ignite vs Redis for our use case these days, and wanted to make sure everything works fine as in docs. Can you

Re: Ignite Expiry Inconsistency with Native Persistence

Hi, There was some well known issue with native persistence and rebalancing data between nodes, later I can try to find its Id . How much nodes do you use? Sincerely, Dmitry Pavlov ср, 7 мар. 2018 г., 22:25 Subash Chaturanga : > Hi team, > With a cache having