Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.8
-
None
-
None
-
Docs Required, Release Notes Required
Description
Apparently scan query ScanQuery (without specifying explicit partition) does not reserve partitions. Consequently when there is a partition movement (unstable topology, e.g. new node joins the cluster) query can read from an invalid (e.g. already destroyed) partition.
It is easy to catch "java.lang.IllegalStateException: Tree is being concurrently destroyed". As it is a consequence of a race condition other exceptions might be possible. See attached reproducer ScanQueryTopologyMappingTest.java.
One possible solution here is to reserve partitions properly. Other approach is to consider some optimistic strategy.
Attachments
Attachments
Issue Links
- is duplicated by
-
IGNITE-1666 Fallback for full scan query does not work
- Resolved