[SERVER-65087] Audit the usage of foreground index builds through IndexBuildsCoordinator::createIndex() Created: 30/Mar/22  Updated: 29/Oct/23  Resolved: 25/May/22

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

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

Issue Links:
Related
related to SERVER-65024 Multiple documents with the same _id ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-05-02, Execution Team 2022-05-16, Execution Team 2022-05-30
Participants:

 Description   

We start a foreground index build through IndexBuildsCoordinator::createIndex() at a couple places (example1, example2). The index builds done through this interface have been ignoring any constraint violations until SERVER-65024 which fixes the duplicate key issues. We should investigate if we can get rid of this code path.

Otherwise, we should add test coverage for it (e.g. on collections with index constraint violations).



 Comments   
Comment by Githook User [ 25/May/22 ]

Author:

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

Message: SERVER-65087 Clarify the usage of `IndexBuildsCoordinator::createIndex()`
Branch: master
https://github.com/mongodb/mongo/commit/859e975fa5d59d673b8fe5c4ef4dc92647ee2138

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