[SERVER-43295] Secondaries should start index build on receiving startIndexBuild oplog entry Created: 12/Sep/19  Updated: 29/Oct/23  Resolved: 13/Sep/19

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

Type: Task Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
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-39239 Two-phase index builds on secondaries... Closed
Related
related to SERVER-43323 replicated index builds not writing s... Closed
related to SERVER-43301 add no_passthrough to two phase index... Closed
is related to SERVER-43024 secondary oplog application should ig... Closed
is related to SERVER-43149 replicated index builds on empty coll... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2019-09-23
Participants:

 Description   

When two phase index builds are enabled, secondaries should be starting an index build on receiving a startIndexBuild oplog entry. Additionally, in this mode, primaries should stop emitting the createIndexBuild oplog entry.



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

Author:

{'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}

Message: SERVER-43295 startIndexBuild kicks off index builds on secondaries
Branch: master
https://github.com/mongodb/mongo/commit/9a18de96023e67ae3ee8888a4745ed923882e49f

Comment by Benety Goh [ 12/Sep/19 ]

SERVER-43149 identifies all the non-IndexBuildsCoordinator code paths where we also emit a createIndexes oplog entry.

Comment by Benety Goh [ 12/Sep/19 ]

This ticket re-enables the startIndexBuild, predicated on a feature flag, that was disabled in SERVER-43024.

Comment by Benety Goh [ 12/Sep/19 ]

Using the startIndexBuild oplog entry to kick off index builds is a prerequisite for SERVER-39239, where we block the completion of the index build until we receive a commitIndexBuild oplog entry.

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