Re: Replicated cache leaks entries on 1.6 and 1.7-SNAPSHOT

Okay, I drove back to work to check this out. It turns out all my troubles were being caused by inconsistent equals/hashCode. The key in the cache was an abstract base class with multiple overrides (which in itself I believe is one of those grayish areas wrt equals/hashCode). I just changed this to

Re: Replicated cache leaks entries on 1.6 and 1.7-SNAPSHOT

Hi Kristian, interesting idea about inconsistent equals/hashCode could you show the code for review you can display cache statistics: cacheCfg.setStatisticsEnabled(true); ... System.out.println("cache.metrics: " + cache.metrics());

Re: Replicated cache leaks entries on 1.6 and 1.7-SNAPSHOT

Denis, you linked back to my own post :) I've left work for the weekend, but there is one piece of information that couldnt leave my head: The database backing of the cache always contains fewer nodes than either of the cluster members, even though there is no reported error. This would actually

Re: Replicated cache leaks entries on 1.6 and 1.7-SNAPSHOT

Kristian, This topic looks similar to the following one [1]. Probably the issue is the same so I would prefer to discuss this in one place if you don’t mind. [1] http://apache-ignite-users.70518.x6.nabble.com/Replicated-cache-leaks-entries-on-1-6-and-1-7-SNAPSHOT-td5704.html

Re: Replicated cache leaks entries on 1.6 and 1.7-SNAPSHOT

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 wrote:

Replicated cache leaks entries on 1.6 and 1.7-SNAPSHOT

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 n