Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- auto-reverted

Assigned Teams:

Query Execution
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v8.2, v8.1, v8.0, v7.0
Sprint:
QE 2025-08-18
Case:
Linked BF Score:
0
Confidence Status:
None
Work Order:
3
Size Category:
TBD
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

See investigation details and repro script in HELP-79061.
A few options to fix it:

Using deadline instead of maxTime to calculate remaining time
Save the original maxTime as well in DeadlineState returned by opCtx->pushArtificialDeadline()
Add elapsed time to maxTime in opCtx->computeMaxTimeFromDeadline()

related to

SERVER-108835 Deadline and maxTime compete for representing maximum operation latency

Open

Assignee:: Zixuan Zhuang
Reporter:: Zixuan Zhuang
Participants:: Githook User, Mihai Andrei, Mothra Jira Bot, Zixuan Zhuang
Votes:: 0 Vote for this issue
Watchers:: 17 Start watching this issue

Created:: Jul 31 2025 11:22:23 PM UTC
Updated:: Aug 08 2025 08:56:10 PM UTC
Resolved:: Aug 08 2025 08:56:10 PM UTC
Confidence Status Last Update:: 07/Aug/25 11:29 PM