-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
CAR Team 2024-09-16, CAR Team 2024-09-30
After SERVER-81190 we added a special check in the commit phase to handle the "system.session" collection in case is created as unsplittable.
Every unsplittable collection should be guaranteed to be found in the local catalog of the primary in case it already exists. This allows the coordinator to early exit. However, for "system.session" the check constantly fails. This will cause the coordinator to
- reach the commit phase
- fail to commit on the sharding catalog (already exist)
- re-try indefinitely
The goal of this ticket is to investigate why system.session fails the check
- depends on
-
SERVER-81190 Support tracking "simple" unsharded collections in the sharding catalog
-
- Closed
-
- related to
-
-
- In Progress
-
-
-
- Closed
-