[ https://issues.apache.org/jira/browse/IGNITE-16031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454640#comment-17454640 ]
Vyacheslav Koptilin commented on IGNITE-16031: ---------------------------------------------- Hello [~timonin.maksim], Well, Scan queries (without partition pinning) do not properly work on unstable topology. This is a known limitation, unfortunately. A very similar problem has been reported here https://issues.apache.org/jira/browse/IGNITE-12591 > ScanQuery returns duplicated data > ---------------------------------- > > Key: IGNITE-16031 > URL: https://issues.apache.org/jira/browse/IGNITE-16031 > Project: Ignite > Issue Type: Bug > Affects Versions: 2.11 > Reporter: Maksim Timonin > Assignee: Maksim Timonin > Priority: Major > > ScanQuery doesn't sync topology version over different nodes, so when query > runs on different node it can run over different topologies and can have > duplicated primary partition. > > ``` > ignite = startGrids(1); > cache = ignite.cache(CACHE); > cache.put(1L, new Person(0, 1)); > cache.put(2L, new Person(1, 0)); > cache.put(3L, new Person(1, 1)); > ScanQuery qry = new ScanQuery(); > startGrid(nodesCnt); > Thread.sleep(10); > List<Cache.Entry<Long, Person>> result = cache.query(qry).getAll(); > assertEquals(3, result.size()); // Sometimes fails, and returns duplicated > key=1 > ``` -- This message was sent by Atlassian Jira (v8.20.1#820001)