[SERVER-43192] fix checks for missing abortIndexBuild fields during oplog application Created: 06/Sep/19  Updated: 29/Oct/23  Resolved: 07/Sep/19

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

Type: Bug Priority: Minor - P4
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
is related to SERVER-39067 Implement new simultaneous index buil... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2019-09-09
Participants:

 Description   

When processing abortIndexBuild entries during secondary oplog application, the server should throw an exception if the oplog entry is missing either of the following fields:

  • indexBuildUUID
  • indexes


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

Author:

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

Message: SERVER-43192 fix abortIndexBuild parsing during secondary oplog application
Branch: master
https://github.com/mongodb/mongo/commit/7485b12be0dea7c5654c70dd2b54475a53adac19

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