Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 6.0.0-rc0
Affects Version/s: None
Component/s: Sharding
Labels:
- PM-2144-Milestone-0

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding EMEA 2022-02-21, Sharding EMEA 2022-03-07, Sharding EMEA 2022-03-21
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

Assignee:: Kaloian Manassiev
Reporter:: Kaloian Manassiev
Participants:: Githook User, Kaloian Manassiev
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Feb 05 2022 03:23:45 PM UTC
Updated:: Oct 29 2023 09:43:01 PM UTC
Resolved:: Mar 11 2022 02:25:54 PM UTC
Confidence Status Last Update:: 05/Feb/22 3:25 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates