SERVER-76486 added a new refine collection shard key coordinator that is authoritative in shards, one of the changes include reducing the number of in-memory variables, to simplify how to maintain them synchronized with the persisted state. One of the changes was storing the collection UUID in the coordinator document, this should work for most of the scenarios, however, the interleaving described in SERVER-78997 might generate a situation where the collection object is trying to be accessed when it shouldn't.
We should add an uassert that prevents that access.
- is caused by
-
SERVER-76486 Make RefineShardKey coordinator authoritative on shards
-
- Closed
-
- related to
-
SERVER-78997 Recreating a sharded timeseries collection as a sharded collection might lead to a read failure
-
- Closed
-