[SERVER-53556] Double-check record existence in validate Created: 04/Jan/21  Updated: 29/Oct/23  Resolved: 17/Feb/21

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

Type: Improvement Priority: Major - P3
Reporter: Louis Williams Assignee: Bynn Lee
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Related
is related to SERVER-54481 Disable double validate in collection... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-02-22
Participants:
Linked BF Score: 0

 Description   

There is a bug described in SERVER-50971 where MongoDB observes a record, and in the same snapshot, reads the record again, but WiredTiger returns WT_NOTFOUND.

Consider adding a "double-check" behavior to collection validation. This would lookup a record immediately after validating it. We may not want to enable this by default due to the amount of extra work, but we could enable this in many of our tests.

The hope is that this extra coverage would uncover similar isolation bugs in the future.



 Comments   
Comment by Githook User [ 16/Feb/21 ]

Author:

{'name': 'Bynn Lee', 'email': 'bynn.lee@mongodb.com', 'username': 'bynn'}

Message: SERVER-53556 Double-check record existence in validate
Branch: master
https://github.com/mongodb/mongo/commit/408b94f30377eb038272903626c3acbf7b5cd3f7

Comment by Geert Bosch [ 15/Jan/21 ]

I'd be OK with that. Just have to make sure to file a 5.0 req ticket for that purpose.

Comment by Louis Williams [ 07/Jan/21 ]

Another idea to avoid slowing down validate: enable this by default and then disable it before we release.

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