[SERVER-44443] background_validation_checkpoint_existence.js incorrectly assumes no checkpoint is taken between create collection and background validate cmd calls Created: 05/Nov/19  Updated: 29/Oct/23  Resolved: 03/Jan/20

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

Type: Bug Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: groomed
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2020-01-13
Participants:
Linked BF Score: 6

 Description   

The test expects here that no checkpoint will be taken between the prior create collection and background validate cmd calls. However, there is nothing preventing the mongod from taking a checkpoint: it's a race.

I recommend converting the JS test into a unit test, where we can control whether and when checkpoints occur. We may or may not have added unit test coverage for this since the JS test was create. We should check validate_state_test.cpp and collection_validation_test.cpp to see whether we have coverage now – in which case we can just delete the JS test.



 Comments   
Comment by Githook User [ 03/Jan/20 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-44443 Use a large 'syncdelay' value in background_validation_checkpoint_existence.js to prevent checkpoints from being taken
Branch: master
https://github.com/mongodb/mongo/commit/1127133d8095c9deb4afa6d36cc22e376a8b0edb

Comment by Gregory Wlodarek [ 07/Nov/19 ]

Do you think that using the pauseCheckpointThread fail point is also a viable option?

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