[SERVER-82668] Remove fsync_deadlock.js from the sharding_csrs_continuous_config_stepdown suite Created: 01/Nov/23 Updated: 01/Nov/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Nandini Bhartiya | Assignee: | Nandini Bhartiya |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 22 | ||||||||
| Description |
|
The fsync_deadlock.js test must be removed from the sharding_csrs_continuous_config_stepdown suite because the timing of the fsyncLock request (which takes a Global S lock) may interfere with the RSTL Global X lock that is required for replication set state changes causing the test to hang. |