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 ignite.getOrCreateCache("cache2a") then of course the
cache will be created with zero backups (default configuration). Avoid
doing that.
Regards,
--
Ilya Kasnacheev
вт, 23 окт. 2018 г. в 11:53, wangsan <wqp1...@gmail.com>:
> 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 !!! set backups=2(diff from the
> issule)
>
> 1. Populate data in both cache1a and cache2a.
> 2. Restart ignite server. It knows about cache1a from the persistent store.
> It doesn’t know about cache2a.
> 3. Don't restart client.Wait for the client to reconnect. Then the cache2a
> basckup will be 0 not 2!
>
> It looks like client reconnect did not carry cacheconfiguration(backups=2)
> but just use cacheName
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
