[SERVER-48683] VectorClockConfigServerTest suffers interference from DistLockManagerImpl Created: 10/Jun/20  Updated: 29/Oct/23  Resolved: 11/Jun/20

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

Type: Bug Priority: Major - P3
Reporter: Kevin Pulo Assignee: Kevin Pulo
Resolution: Fixed Votes: 0
Labels: PM-1645-Milestone-3, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2020-06-15
Participants:
Linked BF Score: 0

 Description   

Although VectorClockConfigServerTest inherits from ConfigServerTestFixture, its tests assume that nothing else is ticking the ClusterTime. However, ConfigServerTestFixture installs an actual DistLockManager, which spawns a ReplSetDistLockPinger thread that performs writes, thereby ticking ClusterTime. If the timing is such that these writes happen before/during the VectorClockConfigServerTest tests, they can cause the tests to fail. Therefore VectorClockConfigServerTest should install a mock DistLockManager.



 Comments   
Comment by Githook User [ 11/Jun/20 ]

Author:

{'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com', 'username': 'devkev'}

Message: SERVER-48683 VectorClockConfigServerTest should use DistLockManagerMock
Branch: master
https://github.com/mongodb/mongo/commit/dba968473d0b4dd3e8c7b31e524d3e8ed20bf6ae

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