[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: |
|
||||||||
| 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. |
| Comments |
| Comment by Githook User [ 17/Mar/22 ] |
|
Author: {'name': 'Christopher Caplinger', 'email': 'christopher.caplinger@mongodb.com', 'username': 'UnicodeSnowman'}Message: |
| 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. |