[SERVER-43647] IndexConsistency constructor should use ValidateState's index list rather than simply durable indexes Created: 26/Sep/19  Updated: 29/Oct/23  Resolved: 26/Sep/19

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

Type: Bug Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2019-10-07
Participants:
Linked BF Score: 6

 Description   

ValidateState does extra filtering regarding what indexes to validate, making sure indexes are ready and in the checkpoint, whereas IndexConsistency does not. Additionally, IndexConsistency currently opens its own cursor and so could be looking at indexes in a different checkpoint than the one used by ValidateState, creating an inconsistent view.



 Comments   
Comment by Githook User [ 26/Sep/19 ]

Author:

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

Message: SERVER-43647 IndexConsistency constructor should use ValidateState's index list rather than simply durable indexes
Branch: master
https://github.com/mongodb/mongo/commit/9650ba8f9fe484d70c7fbdd43f107e34182124a5

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