[SERVER-78155] Test the mongos fsync with lock and fsyncUnlock command. Created: 15/Jun/23 Updated: 17/Jul/23 Resolved: 17/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: | [DO NOT USE] Backlog - Sharding NYC |
| 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: | |||||||||||||
| Description |
|
Test functionality of the mongos fsync with lock and fsyncUnlock command.
|
| Comments |
| Comment by Nandini Bhartiya [ 17/Jul/23 ] |
|
This ticket requires testing the mongos fsyncLock and fsyncUnlock functionality and tests have been added as part of https://jira.mongodb.org/browse/SERVER-78149 and https://jira.mongodb.org/browse/SERVER-78150. Failure to fsync lock the cluster will be tested in |