[SERVER-54577] resharding_collection_cloner_resuming.js relies on history but doesn't set a minFetchTimestamp Created: 16/Feb/21  Updated: 29/Oct/23  Resolved: 22/Feb/21

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

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-02-22, Sharding 2021-03-08
Participants:
Linked BF Score: 20
Story Points: 1

 Description   

Resharding writes a `minFetchTimestamp` value to the resharding document which has the side-effect of pinning history in the storage engine.

However, the `testReshardCloneCollection` command does not execute the code to write a minFetchTimestamp. Thus there's no guarantee the oldest timestamp will keep the history necessary for the command to complete successfully, resulting in spurious test failures.



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

Author:

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

Message: SERVER-54577: Have tests using `testReshardCloneCollection` explicitly preserve history.
Branch: master
https://github.com/mongodb/mongo/commit/48a10f5e9f66cc41a35cab593e55c5f0b749ca3e

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