[SERVER-49973] Get rid of RecoveryDocument Created: 29/Jul/20  Updated: 06/Dec/22  Resolved: 21/Sep/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.7 Required
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Duplicate Votes: 0
Labels: 5.0-cleanup, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-55032 Get rid of ShardingStateRecovery once... Closed
Duplicate
duplicates SERVER-60110 Get rid of ShardingStateRecovery once... Closed
Assigned Teams:
Sharding EMEA
Sprint: Sharding EMEA 2021-10-18
Participants:

 Description   

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.


Generated at Thu Feb 08 05:21:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.