[SERVER-51008] adjust rollback to resume index build from phase 3 (catch up from side table) Created: 17/Sep/20  Updated: 29/Oct/23  Resolved: 30/Sep/20

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.8.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

Issue Links:
Related
related to SERVER-51255 rollback persists resumable index inf... Closed
is related to SERVER-39458 Add continuous draining on secondary'... Closed
is related to SERVER-48419 Extend rollback to recover resumable ... Closed
is related to SERVER-53134 Update Execution Architecture Guide t... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-10-05
Participants:

 Description   

SERVER-48419 adds minimal support for recovering resumable index builds after rollback (recover to timestamp). This ticket follows up on that work to include resuming index builds interrupted during the "drain writes" phase.



 Comments   
Comment by Githook User [ 30/Sep/20 ]

Author:

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

Message: SERVER-51008 Enable resuming index builds in the drain writes phase for rollback
Branch: master
https://github.com/mongodb/mongo/commit/cadb990e1ac4229bcf419f47c82656b6458faf8a

Comment by Benety Goh [ 25/Sep/20 ]

In SERVER-39458, the index build process was modified to periodically drain the side writes table on a secondary until the node receives a commitIndexBuild oplog entry. This change was intended to minimize the window for the final drain.

Comment by Benety Goh [ 17/Sep/20 ]

Part of the scope of this ticket involves determining the level of complexity required to make indexes resumable at the side table draining phase.

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