Hi Kristian, Your test looks absolutely correct for me. However I didn’t manage to reproduce this issue on my side as well.
Alex G., do you have any ideas on what can be a reason of that? Can you recommend Kristian enabling of DEBUG/TRACE log levels for particular modules? Probably advanced logging will let us to pin point the issue that happens in Kristian’s environment. — Denis > On Jun 17, 2016, at 10:02 AM, Kristian Rosenvold <[email protected]> > wrote: > > For ignite 1.5, 1.6 and 1.7-SNAPSHOT, I see the same behaviour. Since > REPLICATED caches seem to be broken on 1.6 and beyond, I am testing > this on 1.5: > > I can reliably start two nodes and get consistent correct results, > lets say each node has 1.5 million elements in a given cache. > > Once I start a third or fourth node in the same cluster, it > consistently gets a random incorrect number of elements in the same > cache, typically 1.1 million or so. > > I tried to create a testcase to reproduce this on my local machine > (https://github.com/krosenvold/ignite/commit/4fb3f20f51280d8381e331b7bcdb2bae95b76b95), > but this fails to reproduce the problem. > > I have two nodes in 2 different datacenters, so there will invariably > be some differences in latencies/response times between the existing 2 > nodes and the newly started node. > > This sounds like some kind of timing related bug, any tips ? Is there > any way I kan skew the timing in the testcase ? > > > Kristian
