[SERVER-77353] Get rid of the Locker implementation for MongoS Created: 22/May/23  Updated: 29/Oct/23  Resolved: 23/May/23

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

Type: Improvement Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: PM-2144-Cleanup
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-77213 Move the all transactions-related sta... Backlog
Problem/Incident
Related
related to SERVER-60229 lock manager for mongos Closed
is related to SERVER-77613 Complete TODO listed in SERVER-60229 Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-05-29
Participants:
Linked BF Score: 55

 Description   

It is unnecessary for MongoS to be acquiring locks in the first place, but there are some code paths that are shared between MongoD and MongoS which require this. However it shouldn't be necessary to have two different locker implementations between the two services.



 Comments   
Comment by Githook User [ 08/Jun/23 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-77353 Delete locker_mongos.h
Branch: master
https://github.com/mongodb/mongo/commit/b505c974a9b803a46aa9a3b2bc11c165c7841ddf

Comment by Githook User [ 28/May/23 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-77353 Fix library linking dependency for Locker
Branch: master
https://github.com/mongodb/mongo/commit/fd6ff146e278795a8e66f2475e1a16728cc9d295

Comment by Githook User [ 23/May/23 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-77353 Get rid of the MongoS-specific locker implementation
Branch: master
https://github.com/mongodb/mongo/commit/f855cee8645a87491c779eb56db3286145234bb8

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