-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 5.0.0, 6.0.0, 7.0.0, 8.1.0-rc0, 8.0.0
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2024-11-25, CAR Team 2024-12-23, CAR Team 2025-01-06
-
2
The config.system.sessions collection is expected to be a sharded collection spread out among the shards. However, if the user tries to use a session before the collection has been created it is possible for the collection to be implicitly created as unsharded. In this case, it will live only on the config server and when the logical sessions cache refresher shards the collection, the unsharded version on the config server will become inaccessible (along with any sessions inside it).
We should prevent this collection from being created as unsharded and should instead create it as sharded if there is a request to create it implicitly.
- is depended on by
-
SERVER-98040 Prevent config.system.sessions from being sharded with incorrect options
- Needs Scheduling
-
SERVER-98119 Sharding system collection can fail in suite with config transition
- Needs Scheduling
- is related to
-
SERVER-86949 Run the shardCollection coordinator on the config server
- In Code Review
- related to
-
SERVER-97338 Prevent config.system.sessions from being created as sharded with its chunk on the config server
- Closed
-
SERVER-98040 Prevent config.system.sessions from being sharded with incorrect options
- Needs Scheduling
-
SERVER-98270 Ban implicit creation and user manipulation for the sessions collection
- Needs Scheduling