[SERVER-43024] secondary oplog application should ignore no-op startIndexBuild entry Created: 23/Aug/19  Updated: 29/Oct/23  Resolved: 31/Aug/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-43295 Secondaries should start index build ... Closed
related to SERVER-45064 Stop replicating startIndexBuild and ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2019-09-09
Participants:

 Description   

While index builds are still writing both startIndexBuild and createIndexes oplog entries, secondary oplog application should continue to process createIndexes but ignore the noop startIndexBuild



 Comments   
Comment by Githook User [ 31/Aug/19 ]

Author:

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

Message: SERVER-43024 secondary oplog application should ignore no-op startIndexBuild entry
Branch: master
https://github.com/mongodb/mongo/commit/927a3e19e74a78219f18aff79a18dc70b2ac5eba

Comment by Githook User [ 31/Aug/19 ]

Author:

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

Message: SERVER-43024 provide default list of acceptable errors for startIndexBuild and reformat
Branch: master
https://github.com/mongodb/mongo/commit/163ab677f210354e6a1dd7d1fb77ad5075c30bd9

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