-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
CAR Team 2025-07-07
-
200
-
None
-
3
-
TBD
-
🟦 Shard Catalog
-
None
-
None
-
None
-
None
-
None
-
None
If the StaleConfig is caused by a resharding critical section, waiting without checking the session back in could make resharding oplog application get stuck trying to check out the session that got checked out when applying oplog entries in the same session as the operation that is stuck waiting for resharding critical section to complete.
- is related to
-
SERVER-61127 Multi-writes may exhaust the number of retry attempts in the presence of ongoing chunk migrations
-
- Closed
-
-
SERVER-91465 Don't Return StaleConfig for UpdateMany on Unsplittable Collections
-
- Closed
-