[SERVER-81921] Create ThreadClients with Service, not ServiceContext Created: 05/Oct/23  Updated: 29/Oct/23  Resolved: 12/Oct/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0

Type: Task Priority: Major - P3
Reporter: George Wangensteen Assignee: George Wangensteen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-80993 (SA) Ensure all process-internal clie... Closed
related to SERVER-81830 Create Clients with Service, not Serv... Closed
Backwards Compatibility: Fully Compatible
Sprint: Service Arch 2023-10-16
Participants:

 Description   

As part of ensuring all internal clients and operations are cluster-role-aware, they can be tagged with the Service (corresponding to a ClusterRole) they are running under. In this ticket, migrate ThreadClients that are being created with a raw ServiceContext to being created via a Service that they are a member of.

For now, just use the "default service" on the ServiceContext, which will be either Router or Shard depending on the binary. After this ticket, we will need to tag them specifically as the use of a "default service" is eliminated.



 Comments   
Comment by Githook User [ 11/Oct/23 ]

Author:

{'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}

Message: SERVER-81921 Create ThreadClients with Service, not ServiceContext
Branch: master
https://github.com/mongodb/mongo/commit/9dff9b5926bb7c08ee39969e4a083af356be49f5

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