Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
Description
Description
SERVER ticket description: null
Change Description:
This enables the Better Predicitive Connection Pool Sizing matchPrimaryNode behavior as default. This will likely cause more connections from mongo/mongos but lower latency on stepdown.
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
Attachments
Issue Links
- documents
-
SERVER-41682 Change default for ShardingTaskExecutorPoolReplicaSetMatching to matchPrimaryNode
-
- Closed
-