Re: npe: Failed to reinitialize local partition

Hello! You can track it on developers list. Should be any day now. Regards, -- Ilya Kasnacheev пн, 29 окт. 2018 г. в 6:53, wangsan : > Hi: > I run the test in v2.5 (with npe patch) , The in_memory cache backups > will be 0 when reconnect. When I use v2.7 ,It's ok! > When v2.7

Re: npe: Failed to reinitialize local partition

Hi: I run the test in v2.5 (with npe patch) , The in_memory cache backups will be 0 when reconnect. When I use v2.7 ,It's ok! When v2.7 release will be released? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: npe: Failed to reinitialize local partition

Hello! Sorry, I was looking at file in a wrong location. Now I can see your test. I have ran it on master and the result is: - wait for client reconnect persisted backups ->1 inmemory backups ->2 If this is the correct result, I think you should expect the correct behaviour in

Re: npe: Failed to reinitialize local partition

Hello! What is the cache template here, and where is it defined? I don't see any changes to the test. Can you modify it so that it will display your case? Regard, -- Ilya Kasnacheev чт, 25 окт. 2018 г. в 5:31, wangsan : > IgniteTwoRegionsRebuildIndexTest.java > < >

Re: npe: Failed to reinitialize local partition

IgniteTwoRegionsRebuildIndexTest.java The file is the test case. I use getOrCreateCache with name. But the cache template I have beed defined before.When reconnect ,It looks like the cache

Re: npe: Failed to reinitialize local partition

Hello! Can you make a simple reproducer of that problem? I have tried to reproduce it but could not observe the backup number changing. Instead, on 2.7 I observe correct number and on 2.6- I observe NPE since cache2a does not exist in the grid. Note that if you run

Re: npe: Failed to reinitialize local partition

Tks! I applyed the patch from the issue.And the NPE was fixed. But another problems happen: As the issue says: Steps to reproduce: Ignite server region1 (with persistence) region2 (without persistence) client cache1a from region1 – with custom affinity cache2a fom region2 – with custom affinity

Re: npe: Failed to reinitialize local partition

Hello! I'm not very familiar with the area of Persistence FS layout, but I imagine this might be caused by the bug we are discussing. Regards, -- Ilya Kasnacheev пт, 19 окт. 2018 г. в 18:00, wangsan : > Thanks! > The ticket description is especially like my scene. I will apply the patch! > >

Re: npe: Failed to reinitialize local partition

Thanks! The ticket description is especially like my scene. I will apply the patch! I have a little confused about the persistence file. If I have a default region without persistence. and cache2a use default region. the db file(directory) won't be created. But if I have region1 (with

Re: npe: Failed to reinitialize local partition

Hello! Looks exactly like a known issue: https://issues.apache.org/jira/browse/IGNITE-9425 It will be fixed in 2.7 which is due real soon. You could also try nightly builds to see if it would help. Or you could try to work-around this problem based on the description from ticket (same cache

npe: Failed to reinitialize local partition

when a c++ node with cache(c++ defined) join the java server node(persistence true). it will throw this exception,When I clear server persistence home then restart.the exception won't throw Why? o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture - Failed to reinitialize local partitions