Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- M2
- join-plan-cache

Assigned Teams:

Query Optimization
CAR Domain/s:
None

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

This ticket should introduce finger-grained metrics for the join plan cache replanning process. For example:

Per-cause replan counters (reads breach vs intermediate results breach vs spill)
Replanned plan is same as original - gives signal on false-positive rate
replanReason in $currentOp and slow query

depends on

SERVER-136737 Record baseline metrics and implement cache-eligibility gate for join plan cache entry

In Code Review

SERVER-136738 Perform a trial run on join plan cache hit and make replanning decision

In Progress

is depended on by

SERVER-136740 Concurrency testing for join plan cache replanning

Backlog

Assignee:: Naafiyan Ahmed
Reporter:: Naafiyan Ahmed
Participants:: Naafiyan Ahmed
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: Oct 09 2026 06:31:11 PM UTC
Updated:: Oct 09 2026 06:37:44 PM UTC