[SERVER-64956] Test Shard Merge with and without enableDonorStartMigrationFsync Created: 25/Mar/22 Updated: 03/Mar/23 Resolved: 03/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | [DO NOT USE] Backlog - Server Serverless (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | shard-merge-milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Serverless
|
||||||||
| Participants: | |||||||||
| Description |
|
Many Shard Merge tests currently use the test framework's enableDonorStartMigrationFsync flag. When this flag is set, the donor executes an fsync before the migration begins. Thus, if we wrote data to the donor before the migration, that data appears in the latest snapshot and it's copied to the recipient via file-copy. If we don't call fsync, then donor data usually doesn't appear in the snapshot. It's copied to the recipient via oplog application instead. We need to thoroughly test both mechanisms for migrating data. Everywhere we use enableDonorStartMigrationFsync, let's test both with and without enableDonorStartMigrationFsync, if possible. |
| Comments |
| Comment by Suganthi Mani [ 03/Mar/23 ] |
|
We no longer need enableDonorStartMigrationFsync. |