[SERVER-41602] Activate followBusiestNode in ShardingTaskExecutor Created: 10/Jun/19  Updated: 29/Oct/23  Resolved: 19/Jun/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.2.0-rc2, 4.3.1

Type: Bug Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Benjamin Caimano (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Service Arch 2019-06-17, Service Arch 2019-07-01
Participants:
Linked BF Score: 20

 Description   

As is, the fBN mode has problems with decreasing its connection target. I've spun this out as a separate ticket to land followPrimaryNode more quickly.



 Comments   
Comment by Githook User [ 19/Jun/19 ]

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}

Message: SERVER-41602 Activate followBusiestNode in ShardingTaskExecutor
Branch: v4.2
https://github.com/mongodb/mongo/commit/8ab1b17cbcc7f5389a933e9864511ce1565fc68e

Comment by Githook User [ 19/Jun/19 ]

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}

Message: SERVER-41602 Activate followBusiestNode in ShardingTaskExecutor
Branch: master
https://github.com/mongodb/mongo/commit/5ad06b7359ccdaafedfa4bc562d2ea8e3bc0c355

Generated at Thu Feb 08 04:58:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.