[SERVER-69356] Stop locking config db in unittest fixtures Created: 01/Sep/22  Updated: 29/Oct/23  Resolved: 24/Oct/22

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

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-65891 Make all distLock acquisitions local-... Closed
is depended on by SERVER-65915 Enforce RSLocalClient::queryOnce does... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-09-05, Sharding EMEA 2022-09-19, Sharding EMEA 2022-10-03, Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31
Participants:

 Description   

Since we removed dist lock and the pinger routine in SERVER-65891  there is no need anymore to lock the config database in our unittest config fixtures.

Remove this TODO



 Comments   
Comment by Githook User [ 16/Sep/22 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-69356 Stop locking config db in unittest fixtures
Branch: master
https://github.com/mongodb/mongo/commit/eb5d4ed00d889306f061428f5652431301feba8e

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