[SERVER-38813] Replace AlternativeOpCtx with AlternativeClientRegion Created: 03/Jan/19  Updated: 29/Oct/23  Resolved: 28/Jan/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.1.8

Type: Task Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Siyuan Zhou
Resolution: Fixed Votes: 0
Labels: neweng, prepare_diagnostics
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-02-11
Participants:

 Description   

A Client is an ordered sequence of OperationContexts, at most one of which is currently active. Developers are allowed to rely on the assumption that an OperationContext will only be current on a Client for one contiguous interval of time. AlternativeOpCtx violates this design and may cause issue for interruptibility and currentOp reporting.
 
Instead, AlternativeClientRegion should be used to start a new Client to do the job.



 Comments   
Comment by Githook User [ 28/Jan/19 ]

Author:

{'username': 'visualzhou', 'email': 'siyuan.zhou@mongodb.com', 'name': 'Siyuan Zhou'}

Message: SERVER-38813 Replace AlternativeOpCtx with AlternativeClientRegion
Branch: master
https://github.com/mongodb/mongo/commit/d0b2a623ee1838ba060713d0ff9bd1ba94d9e7d8

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