[SERVER-62934] Don't require donor fsync before shard merge specific tests. Created: 24/Jan/22  Updated: 29/Oct/23  Resolved: 22/Mar/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: Backlog
Fix Version/s: 6.0.0-rc0

Type: Task Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: Christopher Caplinger
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-61144 Finish importing donated collections ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2022-03-21, Server Serverless 2022-04-04
Participants:

 Description   

In my tenant_migration_file_import.js test, I added an fsync call on the donor before starting the migration. At the time this seemed necessary. Ensure we don't need it anymore.

https://github.com/10gen/mongo/blob/88de0204ddee95aa04ea496087db5c2aa0f359fa/jstests/replsets/tenant_migration_file_import.js#L55



 Comments   
Comment by Githook User [ 17/Mar/22 ]

Author:

{'name': 'Christopher Caplinger', 'email': 'christopher.caplinger@mongodb.com', 'username': 'UnicodeSnowman'}

Message: SERVER-62934: Don't require explicit donor fsync before shard merge specific tests.
Branch: master
https://github.com/mongodb/mongo/commit/49d6e94c2363f27bda8cf4838635b443485d1bd9

Comment by A. Jesse Jiryu Davis [ 27/Jan/22 ]

Maybe donorStartMigration must await w:majority and call fsync before it calls recipientSyncData, to ensure tenants added recently appear in the backup cursor's snapshot.

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