[SERVER-60109] Ensure vector clock is recovered on step-up - MongoDB Jira

XML

Word

Printable

Details

Type: Task
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 5.3.0, 5.0.7, 5.2.2
Component/s: Sharding
Labels:
- sharding-wfbf-sprint

Backwards Compatibility:
Fully Compatible
Backport Requested:

v5.2, v5.0
Sprint:
Sharding EMEA 2021-12-27, Sharding EMEA 2022-01-10

Description

Ticket coming from this comment of ~~SERVER-55032~~.

Tasks to be performed before 6.0 gets released:

Run VectorClock::recover() (in addition to the ShardingStateRecovery::recover()) on stepup
In ShardingStateRecovery::endMetadataOp(), also make configTime durable on VectorClock

Attachments

Issue Links

related to

SERVER-55032 Get rid of ShardingStateRecovery once 5.0 branches out

Closed

Activity

People

Assignee:: Pierlauro Sciarelli

Reporter:: Pierlauro Sciarelli

Participants:: Githook User, Pierlauro Sciarelli

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: Sep 21 2021 03:05:45 PM UTC

Updated:: Mar 01 2022 04:08:21 PM UTC

Resolved:: Jan 04 2022 11:56:13 AM UTC