[SERVER-80823] Remove gRPC uses of getGlobalServiceContext Created: 06/Sep/23  Updated: 18/Sep/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Erin McNulty Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-51700 Use TransportLayer to acquire WireSpec Closed
Assigned Teams:
Service Arch
Participants:

 Description   

When changing WireSpec to be a decorator of ServiceContext (PR Here), we introduced a few uses of getGlobalServiceContext() and getCurrentServiceContext() into the gRPC code:

https://github.com/10gen/mongo/blob/6a836ac18b9530f4a5e0f87a048497eb0686a77d/src/mongo/transport/grpc/test_fixtures.h#L395-L398

https://github.com/10gen/mongo/blob/6a836ac18b9530f4a5e0f87a048497eb0686a77d/src/mongo/transport/grpc/wire_version_provider.cpp#L37-L39

https://github.com/10gen/mongo/blob/6a836ac18b9530f4a5e0f87a048497eb0686a77d/src/mongo/transport/grpc/service.cpp#L101-L103

We should find a way to remove these calls during one of the gRPC projects.



 Comments   
Comment by Erin McNulty [ 18/Sep/23 ]

Worked on during during 9/18 sprint, Blake advised that we send it back to backlog to work on more important issues instead right now.

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