I am also interested in this topic as it's relevant to my use case. Wouldn't you need to configure segmentation policy? https://gridgain.readme.io/docs/network-segmentation
Hazelcast had a concept of merge strategy to recover reconcile data - I'm not sure if Ignite has something similar. -marcus On Thu, Oct 27, 2016 at 7:59 AM, Kristian Rosenvold <krosenv...@apache.org> wrote: > What we don't understand is that after a network failure, we see requests > for data that was processed by node A (replicated cache running write > through) that is not visible to node B. At the time of the request, node B > has no in-memory knowledge of the data (since it was just created by Node > A), and we would expect it to fall through to the database. This does not > seem to happen ? > > This is ignite 1.7.0. > > Kristian > > > 2016-10-27 13:20 GMT+02:00 Vladislav Pyatkov <vldpyat...@gmail.com>: > >> Hi, >> >> It will be working, because replicated cache implemented as partition >> with number of backups equivalent to number of nodes. >> >> On Thu, Oct 27, 2016 at 2:13 PM, Kristian Rosenvold < >> krosenv...@apache.org> wrote: >> >>> Does this configuration actually do anything with a replicated cache, if >>> so what does it do ? >>> >>> Kristian >>> >>> >> >> >> -- >> Vladislav Pyatkov >> > >
