[SERVER-43023] emit no-op startIndexBuild oplog entry on successful createIndexes command Created: 23/Aug/19  Updated: 29/Oct/23  Resolved: 02/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-45064 Stop replicating startIndexBuild and ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2019-09-09
Participants:

 Description   

This replaces the noop message currently written to the oplog.



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

Author:

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

Message: SERVER-43023 IndexBuildsCoordinator emits startIndexBuild oplog entry at the beginning of an index build

This replaces the 'n' (no-op) oplog entry with the message "Creating indexes. Coll: (nss)".
Branch: master
https://github.com/mongodb/mongo/commit/8685992ea1488da7afbad047530d3f18988c2224

Comment by Githook User [ 31/Aug/19 ]

Author:

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

Message: SERVER-43023 apply_ops_idempotency.js filters out startIndexBuild oplog entries during replay
Branch: master
https://github.com/mongodb/mongo/commit/afbd64a6d1351107c217912fdda1324cef9faf1e

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