[SERVER-50471] Waiting for failpoint does not always throw in quiesce_mode.js Created: 21/Aug/20  Updated: 29/Oct/23  Resolved: 24/Aug/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Bug Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Tess Avitabile (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Repl 2020-08-24, Repl 2020-09-07
Participants:
Linked BF Score: 35

 Description   

In quiesce_mode.js, when we wait for the pauseWhileKillingOperationsAtShutdown here and here, we assume that the waitForFailPoint command will be killed by the server, since the server has started killing new operations and marked all existing operations as killed. However, if the waitForFailPoint command was an existing operation, then even though it was marked as killed, it might not have any remaining interrupt points and could complete successfully.



 Comments   
Comment by Githook User [ 24/Aug/20 ]

Author:

{'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}

Message: SERVER-50471 Waiting for failpoint does not always throw in quiesce_mode.js
Branch: master
https://github.com/mongodb/mongo/commit/9de1a21c9bae1f57b4a52f2a8ac5330fedd81acd

Generated at Thu Feb 08 05:22:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.