Ticket coming from this comment of SERVER-55032.
Tasks to be performed right after 7.0 gets released:
- Change migration to no longer use ShardingStateRecovery and use just VectorClock::waitDurable
- ShardingStateRecovery no longer reads or updates it's own configOpTime (we can just rely on VectorClock now)
- depends on
-
SERVER-67862 Make ShardingStateRecovery::endMetadataOp() persist the configTime as a preliminary step for removing ShardingStateRecovery
- Closed
- is depended on by
-
SERVER-65766 ShardingStateRecovery makes remote calls to config server while holding the RSTL
- Closed
- is duplicated by
-
SERVER-49973 Get rid of RecoveryDocument
- Closed
- is related to
-
SERVER-73564 Handle ShardingStateRecovery for catalog shard
- Closed
-
SERVER-78330 Remove ShadingStateRecovery cleanup procedure
- Closed
- related to
-
SERVER-55032 Get rid of ShardingStateRecovery once 5.0 branches out
- Closed