[SERVER-49528] retrieve resumable index build information before stopping index builds for rollback Created: 15/Jul/20  Updated: 29/Oct/23  Resolved: 06/Aug/20

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

Type: Task Priority: Major - P3
Reporter: Benety Goh Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-08-10
Participants:

 Description   

At the beginning of the rollback process, the server stops all in-progess index builds. This is done in both rollback algorithms - Recover to a Timestamp and rollbackViaRefetch.

In order to resume an index build without restarting the index build from the beginning, the Recover to a Timestamp algorithm needs additional information from the IndexBuildsCoordinator on the current state of each in-progress index build. This information will be the same information as what is currently written to disk on a clean shutdown for index builds.

The Recover to a Timestamp rollback algorithm should be able to report the state of each interrupted index build before it starts the actual rollback process. We will use this information to change how rollbacks work for interrupted index builds in SERVER-48419.



 Comments   
Comment by Githook User [ 06/Aug/20 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-49528 Retrieve resumable index build information before stopping index builds for rollback
Branch: master
https://github.com/mongodb/mongo/commit/6522e78360de316c46700bc51f34d3bf0b551e34

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