-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Change streams
-
None
-
DB Integration & Observability
-
Fully Compatible
-
v9.0
-
QI 2025-02-17
-
None
-
None
-
None
-
None
-
None
-
None
-
None
This change makes the following changes to how the optional operationResponseMaxMs deadline is handled in change stream oplog scans:
- Preserve the response deadline across resources releases, i.e. when PlanExecutorImpl calls releaseAllAcquiredResources(). Otherwise the deadline may restart from its original value after resources are re-acquired.
- Also enforce the deadline while waiting for new oplog entries inside insert_listener::waitForInserts(). This makes the deadline apply also in case the oplog scan is already finished and there are no new events inserted.
- Only apply the deadline to the actual change stream oplog scan, but not the other sub-operations in a change stream. Previously, the deadline was honored in the plan executor whenever a change stream spec was set in the ExpressionContext. While this works, it is not narrow enough. The change stream's ExpressionContext is cloned for its sub-executors as well, so an ExpressionContext cloned for updateLookup will also have a change stream spec set on it and honor the deadline. This is now prevented, so only the main oplog scan will honor the deadline.