[SERVER-53373] Have donor shards pin oldest_timestamp as part of choosing their minFetchTimestamp Created: 15/Dec/20  Updated: 29/Oct/23  Resolved: 05/Feb/21

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

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: PM-234-M2.5, PM-234-T-data-clone
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-52789 Create mechanism for pinning the olde... Closed
is depended on by SERVER-54417 Stop enabling WTPreserveSnapshotHisto... Closed
Duplicate
is duplicated by SERVER-53516 Have donor shards re-pin oldest_times... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-01-11, Sharding 2021-01-25, Sharding 2021-02-08
Participants:
Story Points: 1

 Description   
  • This needs to happen on both the donor shard primary as well as any donor shard secondaries.
  • Usages of the WTPreserveSnapshotHistoryIndefinitely failpoint within reshardCollection tests should be removed.


 Comments   
Comment by Githook User [ 05/Feb/21 ]

Author:

{'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}

Message: SERVER-53373: Pin resharding durable history across restart.
Branch: master
https://github.com/mongodb/mongo/commit/674d57fc70d80dedbfd634ce00ca4b967ea89646

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