[SERVER-41132] Support parallel targeting of hosts in the ARS Created: 13/May/19  Updated: 29/Oct/23  Resolved: 06/Jun/19

Status: Closed
Project: Core Server
Component/s: Internal Code, Sharding
Affects Version/s: None
Fix Version/s: 4.2.0-rc1, 4.3.1

Type: New Feature Priority: Major - P3
Reporter: Mira Carey Assignee: Mira Carey
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Documented
is documented by DOCS-12785 Docs for SERVER-41132: Support parall... Closed
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.2
Sprint: Service Arch 2019-06-03, Service Arch 2019-06-17
Participants:
Linked BF Score: 17

 Description   

Inside the ARS, support use of the TaskExecutor::scheduleRemoteCommandOnAny method, which will allow the ARS to use any acceptable host returned from targeting, rather than requiring us to use one at random.

This should allow us to prefer routing requests to hosts which have ready connections to, or that we can generate ready connections to faster



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

Author:

{'name': 'Jason Carey', 'email': 'jcarey@argv.me', 'username': 'hanumantmk'}

Message: SERVER-41132 Opportunistic targeting for ARS

Inside the ARS, support use of the
TaskExecutor::scheduleRemoteCommandOnAny method, which will allow the
ARS to use any acceptable host returned from targeting, rather than
requiring us to use one at random.

This should allow us to prefer routing requests to hosts which have
ready connections to, or that we can generate ready connections to
faster

(cherry picked from commit 8eed2fe5376ff6843ab1fe7881c8377812215185)
Branch: v4.2
https://github.com/mongodb/mongo/commit/4fc54eade0028a9976f6c2556fa7c169f66f2ba0

Comment by Githook User [ 06/Jun/19 ]

Author:

{'name': 'Jason Carey', 'email': 'jcarey@argv.me', 'username': 'hanumantmk'}

Message: SERVER-41132 Opportunistic targeting for ARS

Inside the ARS, support use of the
TaskExecutor::scheduleRemoteCommandOnAny method, which will allow the
ARS to use any acceptable host returned from targeting, rather than
requiring us to use one at random.

This should allow us to prefer routing requests to hosts which have
ready connections to, or that we can generate ready connections to
faster
Branch: master
https://github.com/mongodb/mongo/commit/8eed2fe5376ff6843ab1fe7881c8377812215185

Comment by Githook User [ 06/Jun/19 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: Revert "SERVER-41132 Opportunistic targeting for ARS"

This reverts commit f3d9452220039ba74c68fe58b382a237d4e07ad1.
Branch: master
https://github.com/mongodb/mongo/commit/5cca4f2842fc4146604768ed8c95a20aaa955b9d

Comment by Githook User [ 06/Jun/19 ]

Author:

{'name': 'Jason Carey', 'email': 'jcarey@argv.me', 'username': 'hanumantmk'}

Message: SERVER-41132 Opportunistic targeting for ARS

Inside the ARS, support use of the
TaskExecutor::scheduleRemoteCommandOnAny method, which will allow the
ARS to use any acceptable host returned from targeting, rather than
requiring us to use one at random.

This should allow us to prefer routing requests to hosts which have
ready connections to, or that we can generate ready connections to
faster
Branch: master
https://github.com/mongodb/mongo/commit/f3d9452220039ba74c68fe58b382a237d4e07ad1

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