[SERVER-53689] Avoid DistLockManager to run in KeyGeneratorUpdateTest Created: 11/Jan/21  Updated: 29/Oct/23  Resolved: 12/Jan/21

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

Type: Bug Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
is caused by SERVER-53227 Move the DistLock to only be availabl... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-01-25
Participants:
Linked BF Score: 0

 Description   

DistLockManger was avoided to run in KeyGeneratorUpdateTest by using its mocked version of it. The installation of the mocked DistLockManager was recently removed in SERVER-53227 causing several bugs.
As mentioned in the removed comment, the mocked distLockManager is installed in order to avoid the lock pinger thread from executing and accessing uninitialized states.



 Comments   
Comment by Githook User [ 12/Jan/21 ]

Author:

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

Message: SERVER-53689 Make only the ReplSetDistLockManager tests use a mocked lock manager
Branch: master
https://github.com/mongodb/mongo/commit/460b587740c5fa0504ecbf69191c00a7154713da

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