-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2020-03-23, Sharding 2020-04-06, Sharding 2020-04-20
As part of the Make Migration Commit Protocol Robust project, we want to make sure that every function on the CollectionShardingState API do not allow unintended usage if the collection metadata is unknown
- depends on
-
SERVER-46981 The MongoS write commands scheduler does not account for the potential size of the response BSON
- Closed
-
SERVER-46593 Remove locks from ShardServerProcessInterface by directly accessing the routing info
- Closed
- is depended on by
-
SERVER-32198 Missing collection metadata on the shard implies both UNSHARDED and "metadata not loaded yet"
- Closed
- related to
-
SERVER-47492 Complete TODO listed in SERVER-46703
- Closed