[SERVER-68186] Reconcile index table metadata during startup if there is a mismatch caused by collMod Created: 20/Jul/22  Updated: 29/Oct/23  Resolved: 08/Aug/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

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

Issue Links:
Depends
Related
is related to SERVER-68216 Investigate atomicity issue with wire... Backlog
is related to WT-9613 Make alter transactional with updates... Backlog
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2022-08-08, Execution Team 2022-08-22
Participants:
Linked BF Score: 18

 Description   

The wiredtiger call alter() is not transactional, which means that there could be a short window of inconsistency as the changes to the index table file could be visible before the index catalog entry update commits. If this inconsistent state is checkpointed or used as the snapshot for fcbis, we need to reconcile the index table metadata using the catalog entry state during startup, as the call to alter() will always precede the catalog change. We can write an extra field to the index table metadata to differentiate from actual data corruptions on the table.



 Comments   
Comment by Githook User [ 08/Aug/22 ]

Author:

{'name': 'Yuhong Zhang', 'email': 'yuhong.zhang@mongodb.com', 'username': 'YuhongZhang98'}

Message: SERVER-68186 Reconcile index table metadata during startup if there is a mismatch to the index type
Branch: master
https://github.com/mongodb/mongo/commit/e48f8c6dd6fd3568863c64228b9e28562650906b

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