-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 4.7 Required
-
Component/s: Sharding
-
Sharding EMEA
-
Sharding EMEA 2021-10-18
The RecoveryDocument is currently tracking the minOpTime to ensure v4.4 compatibility: not having it would be a problem when downgrading from v4.6 to v4.4 or in case of mixed mongod versions.
Since - starting from v4.6 - the VectorClock persistence/recovery is ensuring casual consistency of the configOpTime, the RecoveryDocument can just be deleted starting from next versions.
- depends on
-
SERVER-55032 Get rid of ShardingStateRecovery once 5.0 branches out
- Closed
- duplicates
-
SERVER-60110 Get rid of ShardingStateRecovery once 7.0 branches out
- Closed