-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Workload Resilience
-
WR Prioritized list
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The IRRL currently is enabled based on a combination signal of CPU pressure and read/write EC queuing time, and it rate limits all requests equally. This has the side effect of throttling reads when only the write queue is backed up and vice-versa. Since we have to parse the request to queue anyways, we should consider introducing the ability to throttle reads and writes separately, at least when queuing is enabled.
- is related to
-
SERVER-136111 Exempt resource-freeing commands such as killCursors in IRRL
-
- Open
-