[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:
Duplicate
duplicates SERVER-71849 Named Pipes: Extend reader retry loop... Closed
duplicates SERVER-78149 Implement the mongos fsync (lock : tr... Closed
Assigned Teams:
Sharding NYC
Participants:

 Description   

Test functionality of the mongos fsync with lock and fsyncUnlock command.

    • Ensure reads are possible but, writes are blocked after the cluster has been locked by the fsync lock command.
    • Ensure writes are possible after executing the fsyncUnlock command
    • Add failure scenarios (fail to fsync lock the cluster and fsync unlock the cluster).


 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 SERVER-78793 & SERVER-78157.

Generated at Thu Feb 08 06:37:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.