Problem Statement
config.system.sessions is not automatically recreated after a drop in 4.0.
Proposed Solution
- Create a method in SessionsCollection named onSessionsCollectionDropped. This method would be a no-op everywhere except for the config server child class, where we would flip the _collectionSetUp boolean to false.
- Expose the SessionsCollection to outside callers through a new LogicalSessionCache method. If we decide this isn't alright, we can just mirror the sessions collection with onSessionsCollectionDropped.
- Hook into the config server opObserver onCollectionDropped to get the SessionsCollection and call onSessionsCollectionDropped.
- Create a ticket to consider making the LogicalSessionCache or SessionsCollection its own opObserver.
Rejected Solutions
- Create an opObserver for the SessionsCollection. We think that this is overkill for the current bugfix.
- is duplicated by
-
SERVER-39044 Cannot add session into the cache error code 261
- Closed
-
SERVER-36904 Fuzzer drops config.system.sessions and triggers invariant
- Closed