-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
CAR Team 2025-04-14, CAR Team 2025-04-28, CAR Team 2025-05-12
-
2
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
This ticket proposes the encapsulation of the existing logic related to the 'c' oplog entry (onDatabaseMetadataUpdate), managing rollbacks and restarts (onConsistentDataAvailable), and managing the critical section into a new class dedicated to maintaining those caches and critical section.
The proposed methods for this class include:
- OnInitialDataAvailable
- OnCriticalSectionStart
- OnCOplogEntry
- OnCriticalSectionEnd
By implementing these methods, we can unit test the class to ensure that the designed model is functioning correctly and that there are no gaps in its implementation.
- depends on
-
SERVER-98135 Recover the temporary DSS from config.shard.databases during rollback
-
- Closed
-
-
SERVER-98136 Recover the temporary DSS from config.shard.databases at startup
-
- Closed
-
-
SERVER-99804 Update the 'c' oplog entry (databaseMetadataUpdate) to fill a temporary DSS
-
- Closed
-
-
SERVER-100036 Implement CRUD path for authoritative database versioning
-
- Closed
-
- related to
-
SERVER-104542 Complete TODO listed in SERVER-100711
-
- Closed
-
-
SERVER-104982 Modularize the ShardingState similarly to the DSS
-
- Needs Scheduling
-
- split to
-
SERVER-103711 Replace setter methods from DatabaseShardingRuntime with a new dedicated class
-
- Open
-
-
SERVER-103712 Unify database version comparisons from FilteringMetadataCache and DatabaseShardingState
-
- Open
-
-
SERVER-103710 Create a mock for DatabaseShardingState to be used by unit tests
-
- In Progress
-
-
SERVER-103708 ShardServerOpObserver must only react to the oplog ācā entry for createDatabase and dropDatabase
-
- Closed
-
-
SERVER-103709 Separate responsibilities currently held by the DSS into a public interface and a private one
-
- Closed
-