Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: 4.7 Required
Component/s: Sharding
Labels:
- 5.0-cleanup
- sharding-wfbf-day

Assigned Teams:

Sharding EMEA
Sprint:
Sharding EMEA 2021-10-18
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: [DO NOT USE] Backlog - Sharding EMEA
Reporter:: Pierlauro Sciarelli
Participants:: [DO NOT USE] Backlog - Sharding EMEA, Pierlauro Sciarelli
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Jul 29 2020 11:00:38 AM UTC
Updated:: Dec 06 2022 02:13:56 AM UTC
Resolved:: Sep 21 2021 03:08:01 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates