[SERVER-46619] Move Baton to Client Created: 04/Mar/20  Updated: 06/Dec/22  Resolved: 20/Apr/20

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

Type: Improvement Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Backlog - Service Architecture
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-46514 Normalize host selection for mirrored... Closed
Related
related to SERVER-47666 Complete TODO listed in SERVER-46619 Closed
Assigned Teams:
Service Arch
Backport Requested:
v4.4
Sprint: Service Arch 2020-03-09, Service Arch 2020-03-23, Service Arch 2020-04-06, Service arch 2020-04-20
Participants:

 Description   

Each OperationContext has its own Baton attached here. We can instead attach the Baton to the Client and have each OperationContext have a SubBatonHolder instead. This may affect performance in unforeseen ways, so this will require general perf verification. Also note that the AsyncRequestsSender will now be making a SubBaton of a SubBaton.



 Comments   
Comment by Githook User [ 21/Apr/20 ]

Author:

{'name': 'Amirsaman Memaripour', 'email': 'amirsaman.memaripour@mongodb.com', 'username': 'samanca'}

Message: SERVER-47666 Remove TODO listed in SERVER-46619 (closed as Won't Fix)
Branch: master
https://github.com/mongodb/mongo/commit/090a4336c8a7105085a69ad02bf8433e5b5a66e9

Comment by Mira Carey [ 20/Apr/20 ]

Closed as wontfix under the assumption that we've addressed the performance of high mirroring rates through another channel.

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