[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: |
|
||||||||
| Issue Links: |
|
||||||||
| 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 |
| Comments |
| Comment by Githook User [ 08/Dec/20 ] |
|
Author: {'name': 'Amirsaman Memaripour', 'email': 'amirsaman.memaripour@mongodb.com', 'username': 'samanca'}Message: |
| Comment by Benjamin Caimano (Inactive) [ 25/Sep/20 ] |
|
divjot.arora, fair enough. We can try to get this assigned out next sprint. |