[SERVER-43323] replicated index builds not writing startIndexBuild and commitIndexBuild oplog entries Created: 13/Sep/19  Updated: 29/Oct/23  Resolved: 30/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: Benety Goh Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-43692 enable two phase index builds by default Closed
Related
is related to SERVER-43149 replicated index builds on empty coll... Closed
is related to SERVER-43295 Secondaries should start index build ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2019-10-07
Participants:

 Description   

In SERVER-43149 and SERVER-43295, we updated a number of components that build indexes that have to be replicated to downstream nodes. There are still a few instances where we write a createIndexes oplog entry to the oplog without the corresponding startIndexBuild and commitIndexBuild oplog entries. These include:



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

Author:

{'name': 'Louis Williams', 'username': 'louiswilliams', 'email': 'louis.williams@mongodb.com'}

Message: SERVER-43323 All replicated index builds should write startIndexBuild
and commitIndexBuild oplog entries

This emits the two-phase oplog entries in cloner.cpp, system_index.cpp and
index_builder.cpp.
Branch: master
https://github.com/mongodb/mongo/commit/3bd5a68827f73f0f3717cb21e725301c8d2cd480

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