-
Type: Improvement
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Service Arch
The ServiceExecutor interface is currently Client agnostic. This has two notable complications:
- When we schedule onto the ServiceExecutorSynchronous from off thread, we start a new thread.
- We cannot easily set context (like thread names and current Client) based on ServiceExecutor details.
- related to
-
SERVER-54510 Bind ClientStrand before destroying its opCtx
- Closed