-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Execution Team 2023-01-09
-
20
Suppose a query is running against an unsharded collection and a concurrent 'shardCollection' shards the collection and a 'moveChunk' moves a chunk away from the primary shard. When the query yields and reacquires a snapshot of the collection, it's not clear whether there's anything that will protect the query from 'observing' that the collection has not only become sharded, but also some of the data has moved away from the primary shard. This ticket tracks the work to write a test that demonstrates the current behavior of the above scenario.
- depends on
-
SERVER-69445 Implement the CollectionSnapshot(s) infrastructure to back CollectionPtr
- Closed
- is depended on by
-
SERVER-64049 Investigate read behavior of unsharded/sharded collections during yields
- Closed
- is related to
-
SERVER-78071 A targeted query with a concurrent yield and chunk migration can miss results
- Backlog