[SERVER-50130] maxTimeMS does not expire if used with the failCommand blockConnection option Created: 05/Aug/20  Updated: 08/Jan/24  Resolved: 08/Dec/20

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

Type: Bug Priority: Major - P3
Reporter: Divjot Arora (Inactive) Assignee: Amirsaman Memaripour
Resolution: Fixed Votes: 0
Labels: neweng, servicearch-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File blockconnection.js    
Issue Links:
Related
related to SERVER-51078 waitWhileFailPointEnabled() interrupt... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Service arch 2020-11-30, Service arch 2020-12-14
Participants:

 Description   

If failCommand is used to block an operation for 1 second and the operation is run with maxTimeMS=100, it succeeds rather than failing with a MaxTimeMSExpired error. Repro script attached

blockconnection.js



 Comments   
Comment by Githook User [ 08/Dec/20 ]

Author:

{'name': 'Amirsaman Memaripour', 'email': 'amirsaman.memaripour@mongodb.com', 'username': 'samanca'}

Message: SERVER-50130 Ensure maxTimeMS can expire if used with the failCommand blockConnection option
Branch: master
https://github.com/mongodb/mongo/commit/24962a20a082f7b95d20b841e6bd3fd3835fa5bc

Comment by Benjamin Caimano (Inactive) [ 25/Sep/20 ]

divjot.arora, fair enough. We can try to get this assigned out next sprint.

CC ratika.gandhi matthew.tretin.

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