Re: Ignite 2.3 - replicated cache lost data after restart cluster nodes with persistence enabled

Hi, I've created issue for this case: https://issues.apache.org/jira/browse/IGNITE-6792 Reproducer is attached to JIRA, also test was added into branch. According to my brief testing, cache.size() method also returns less count than initial load. Sincerely, Dmitriy Pavlov пт, 27 окт. 2017 г. в

Re: Ignite 2.3 - replicated cache lost data after restart cluster nodes with persistence enabled

Hi Denis, I had short chat with Alex G. You're right, It may be a bug. I'll prepare my reproducer and add is as test. Also I will raise the ticket if count(*) will give incorrect result. Sincerely, Dmitry Pavlov пт, 27 окт. 2017 г., 1:48 Denis Magda : > Dmitriy, > > I

Re: Ignite 2.3 - replicated cache lost data after restart cluster nodes with persistence enabled

Dmitriy, I don’t see why a result of a simple query such as “select count(*) from t;” should be different if a rebalancing is in progress or after a cluster restart. Ignite’s SQL engine claims that its fault-tolerant and returns a consistent result set all the times unless a partition loss

Re: Ignite 2.3 - replicated cache lost data after restart cluster nodes with persistence enabled

Hi Denis It seems to me that this is not a bug for my scenario, because the data was not loaded within the same transaction using transactional cache. In this case it is ok that cache data is rebalanced according to partition update counters,isn't it? I suppose in this case the data was not lost

Re: Ignite 2.3 - replicated cache lost data after restart cluster nodes with persistence enabled

+ dev list This scenario has to be handled automatically by Ignite. Seems like a bug. Please refer to the initial description of the issue. Alex G, please have a look: To reproduce: 1. create a replicated cache with multiple indexedtypes, with some indexes 2. Start first server node 3. Insert