[SERVER-42762] recover to timestamp should ignore no-op commitIndexBuild Created: 12/Aug/19  Updated: 29/Oct/23  Resolved: 15/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-43025 rollback should ignore no-op startInd... Closed
is related to SERVER-39451 Add recover to a stable timestamp log... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2019-08-26
Participants:

 Description   

This supports the changes in SERVER-42760 which introduces a no-op commitIndexBuild. Rollback to timestamp should not abort on a no-op commitIndexBuild. This logic will be revisited in SERVER-39451.



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

Author:

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

Message: SERVER-42762 rollback to timestamp ignores commitIndexBuild
Branch: master
https://github.com/mongodb/mongo/commit/6f65e551bf2ac23d84c4655a6fc71f61846a036b

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