-
Type: New Feature
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Service Arch 2020-08-24, Service arch 2020-09-07, Service arch 2020-10-05, Service arch 2020-11-02, Service arch 2020-11-16, Service arch 2020-11-30, Service arch 2020-12-14
Once we have a fixed thread pool ServiceExecutor, we should attach it as the initial executor for new external clients. Once a connection is auth'd (if auth is enabled), we should switch the client to the ServiceExecutorSynchronous. We might want to be more discerning, but auth is the minimum criteria.
- depends on
-
SERVER-49073 Track maxConns exempt connections
- Closed
-
SERVER-49105 Create fixed thread pool ServiceExecutor
- Closed
-
SERVER-48980 Associate ServiceExecutors with Clients
- Closed
-
SERVER-51278 Introduce ClientStrand
- Closed
-
SERVER-51279 Update runOnDataAvailable for async
- Closed
-
SERVER-51280 ServiceExecutorFixed tracks work and sessions
- Closed
- is depended on by
-
SERVER-51280 ServiceExecutorFixed tracks work and sessions
- Closed
- is duplicated by
-
SERVER-52106 Create feature flag for Fixed thread pool to process client connections during handshaking
- Closed
- is related to
-
SERVER-51499 Separate statistics per ServiceExecutor
- Closed