-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Server Programmability
-
Fully Compatible
-
ALL
-
Programmability 2024-09-30, Programmability 2024-10-14
-
200
The RouterRole ServiceEntryPoint benchmark uses the router role service entry point, but creates it's client/opCtx using the shard Service. This means decoration accesses, etc in the code path the benchmark measures will use the shard-role Service, which differs from the production use of this code path. We should ensure we use the right Service for opCtx creation for each benchmark.
- causes
-
SERVER-95420 Set SEP benchmark global cluster role back to what it was after tearing down benchmark.
- Backlog
- is related to
-
SERVER-93915 Invariant that correct service is used on opCtx in ServiceEntryPoint
- In Code Review