[DOCS-12909] Investigate changes in SERVER-41682: Change default for ShardingTaskExecutorPoolReplicaSetMatching to matchPrimaryNode Created: 24/Jul/19  Updated: 13/Nov/23  Resolved: 10/Aug/19

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: 4.3.1, 4.2.0-rc2, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-41682 Change default for ShardingTaskExecut... Closed
Duplicate
Participants:
Days since reply: 4 years, 26 weeks, 5 days ago
Epic Link: DOCS: 4.2 Server/Tools

 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.)



 Comments   
Comment by Githook User [ 10/Aug/19 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-12909: 4.2 ShardingTaskExecutorPoolReplicaSetMatching
Branch: master
https://github.com/mongodb/docs/commit/75e2b6855336cc8d643e30b07bfab72ed83d8bc2

Generated at Thu Feb 08 08:06:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.