[SERVER-78157] Test the mongos fsync lock command while DDL operations are in progress. Created: 15/Jun/23 Updated: 27/Jul/23 Resolved: 27/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Nandini Bhartiya | Assignee: | Jada Lilleboe (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding NYC
|
||||||||
| Participants: | |||||||||
| Story Points: | 2 | ||||||||
| Description |
|
Add tests to verify that the fsync with lock command fails in case any in progress DDL operations are detected on any shard and the locked shards are left in an unlocked state, add a write operation immediately after failing the fsync with lock command. Ensure no DDL operations are queued after the fsync lock has been taken successfully. |
| Comments |
| Comment by Nandini Bhartiya [ 27/Jul/23 ] |
|
Required tests have been added as part of |