[SERVER-54140] DBDirectClient shouldn't unexpectedly modify opCtx Created: 29/Jan/21  Updated: 25/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Jordi Serra Torrens Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: servicearch-wfbf-day, techdebt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Participants:
Story Points: 5

 Description   

As part of SERVER-53935 we realized that DBDirectClient was unexpectedly modifying the readConcernArgs in the callers opCtx.

This ticket is to consider using an AlternativeClientRegion in DBDirectClient so that there is no possibility that the callers opCtx is modified unexpectedly. Instead, callers will need to explicitly transfer any state they wish for a client to inherit (e.g. readConcern, maxTimeMs)

 

Acceptance criteria:

DBDirectClient doesn't unexpectedly modify opCtx. 



 Comments   
Comment by Lauren Lewis (Inactive) [ 24/Feb/22 ]

We haven’t heard back from you for at least one calendar year, so this issue is being closed. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Generated at Thu Feb 08 05:32:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.