[ https://issues.apache.org/jira/browse/IGNITE-16406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vyacheslav Koptilin updated IGNITE-16406: ----------------------------------------- Ignite Flags: (was: Docs Required,Release Notes Required) > SQL select operation could return incomplete data > ------------------------------------------------- > > Key: IGNITE-16406 > URL: https://issues.apache.org/jira/browse/IGNITE-16406 > Project: Ignite > Issue Type: Bug > Reporter: Mirza Aliev > Assignee: Mirza Aliev > Priority: Major > Labels: ignite-3 > > For some reasons select operation couldn't return expected number of rows. We > noticed that this happens when raft leader is changing. To increase > reproducibility, we can slow down a bit message handling, for example by > adding this code to {{MessageServiceImpl#onMessage(java.lang.String, > org.apache.ignite.network.NetworkMessage)}} > {code:java} > if (ThreadLocalRandom.current().nextInt(3) % 2 == 0) { > try { > Thread.sleep(300); > } catch (Exception ex) { > ex.printStackTrace(); > } > } > {code} > Possible direction of research: > we could check that we do not lose cursor.next command as a raft response > during the process of leader changing -- This message was sent by Atlassian Jira (v8.20.1#820001)