[SERVER-51144] Additional sanity checks to validate the metadata for indexes Created: 24/Sep/20  Updated: 29/Oct/23  Resolved: 03/Nov/20

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

Type: Task Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Lingzhi Deng
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-11-02, Execution Team 2020-11-16
Participants:

 Description   

Investigate whether we need to do additional sanity check to validate the metadata for indexes



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

Author:

{'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}

Message: SERVER-51144: Index metadata sanity check for importCollection
Branch: master
https://github.com/mongodb/mongo/commit/3260fb5ffbe18ea62ce15f3c47d7efa02ffdb328

Comment by Githook User [ 03/Nov/20 ]

Author:

{'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}

Message: SERVER-51144: Index metadata sanity check for importCollection
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/bba41cb6ee4dc734ae289523e05ebce02c6e32a8

Comment by Lingzhi Deng [ 25/Sep/20 ]

I am hoping as part of IndexCatalogImpl::init and IndexCatalogImpl::createIndexEntry, we will detect that invalid indexes. Same as how we detect corruption at startup. But we will probably need a different flag for createIndexEntry though so that we dont crash on invalid index.

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