-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2020-03-09, Sharding 2020-03-23, Sharding 2020-04-06, Sharding 2020-04-20
If a call to getCollectionDescription is issued, we must make sure the collection information is known, that is, a refresh should've been called previously. If the data of the collection is unkown, throw a Stale Shard Version Exception. Make sure that all code paths are handling the exception appropriately.
- depends on
-
SERVER-45780 Rename getCurrentMetadata to getCollectionDescription and change the return type
- Closed
- has to be done before
-
SERVER-45782 Remove usages of getCurrentShardVersionIfKnown and most of getCurrentMetadataIfKnown
- Closed
- is depended on by
-
SERVER-32198 Missing collection metadata on the shard implies both UNSHARDED and "metadata not loaded yet"
- Closed
-
SERVER-47412 Make the database cloner ensure collections are actually unsharded before cloning
- Closed
-
SERVER-47413 Some transaction tests are not being retried on Transient Error
- Closed
-
SERVER-47419 Find a better way of setting the shardId when throwing on getCollectionDescription
- Closed