-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding EMEA 2022-02-21, Sharding EMEA 2022-03-07, Sharding EMEA 2022-03-21
The StaleShardVersion error code has been supplanted by StaleConfig which contains a lot more information necessary in order to advance the logical clock of the collection versions. From 6.0 onward there should be no new usages of StaleShardVersion and instead everything should use StaleConfig which eventually will become on par with WriteConflictException.
This ticket is about switching all non-backwards compatibility-breaking usages of StaleShardVersion to StaleConfig in preparation for throwing it out in 6.1.
- causes
-
SERVER-64558 Wait for db critical section on StaleDbVersion
- Closed
-
DRIVERS-2387 Spec test "change stream resumes after StaleShardVersion" fails on server version > 6.0
- Closed
- depends on
-
SERVER-63331 Use a proper IDL structure for the write commands' error reporting
- Closed
- is depended on by
-
SERVER-58116 StaleShardVersion error not triggering a refresh in moveChunk
- Closed
- related to
-
SERVER-64449 Get rid of the StaleShardVersion exception
- Closed