Kristian, it is likely an environment problem, rather than Ignite problem. Can you create a simple reproducer that starts 2 nodes in the same JVM and proves that data is not replicated? If the problem is in Ignite, we will fix it asap.
On Thu, Jun 16, 2016 at 10:58 PM, Kristian Rosenvold <[email protected]> wrote: > We're using a cache with CacheMode.REPLICATED. > > Using 2 nodes, I start each node sequentially and they both get the > same number of elements in their caches (as expected so far). > > Almost immedately, the caches start to drift out sync, all of the > elements are simply not getting replicated. There is nothing in the > log to indicate anything peculiar happening. > > Downgrading to 1.5 makes this problem go away. > > Any suggestions ? > > > Kristian >
