Hi, I’ve tried your test and it works as expected, with some partitions lost and the final size being ~850 (~150 less than on the start). Am I missing something?
Thanks, Stan From: Roman Novichenok Sent: 2 октября 2018 г. 22:21 To: [email protected] Subject: Re: Partition Loss Policy options Anton, thanks for quick response. Not sure if I'm setting wrong expectations. Just tried sql query and that exhibited the same behavior. Created a pull request with a test: https://github.com/novicr/ignite/pull/3. The test goes through the following steps: 1. creates a 4 node cluster with persistence enabled. 2. creates 2 caches - with setBackups(1) 3. populates caches with 1000 elements 4. runs a sql query and prints result size: 1000 5. stops 2 nodes 6. runs sql query from step 4 and prints result size: (something less than 1000). Thanks, Roman On Tue, Oct 2, 2018 at 2:07 PM Roman Novichenok <[email protected]> wrote: I was looking at scan queries. cache.query(new ScanQuery()) returns partial results. On Tue, Oct 2, 2018 at 1:37 PM akurbanov <[email protected]> wrote: Hello Roman, Correct me if I'm mistaken, you are talking about SQL queries. That was fixed under https://issues.apache.org/jira/browse/IGNITE-8927, primary ticket is https://issues.apache.org/jira/browse/IGNITE-8834, will be delivered in 2.7 release. Regards, Anton -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
