[SERVER-13322] Check for interrupts more frequently for killed/maxTimeMS checks Created: 24/Mar/14  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Admin, Concurrency, Internal Code
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: PM-265, interrupts, killop, maxTimeMS, yielding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Execution
Participants:

 Description   

In commands and operations the server should check if there are interrupts (to respond to kill requests or maxTimeMS limits) to react more timely.

Yielding and checking for interrupts are strongly tied together in code (in so much as the yielding code checks for interrupt) but callers should sep. them because while it might not be okay to yield at some points, it is okay to terminate or generate an error for the operation.

A few examples include common commands like count, distinct, findAndModify, update/delete/insert, etc...


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