[SERVER-43025] rollback should ignore no-op startIndexBuild oplog entry Created: 23/Aug/19  Updated: 29/Oct/23  Resolved: 30/Aug/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.2.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
is related to SERVER-42762 recover to timestamp should ignore no... Closed
is related to SERVER-42763 rollback via refetch should ignore no... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2019-09-09
Participants:

 Description   

Both refetch and recover to timestamp rollback algorithm should not crash on trying to rollback a no-op startIndexBuild oplog entry.



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

Author:

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

Message: SERVER-43025 rollback ignores startIndexBuild
Branch: master
https://github.com/mongodb/mongo/commit/79fd21594bbee0323c5d80e5f089a2c87db7639e

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