[SERVER-45174] rollback should not abort single phased index builds Created: 16/Dec/19  Updated: 29/Oct/23  Resolved: 23/Jan/20

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

Type: Bug 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
Related
related to SERVER-45409 Rollback-via-refetch should wait for ... Closed
is related to SERVER-30818 Wait for any running background index... Closed
is related to SERVER-39484 Add step-up and step-down state trans... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2020-01-27
Participants:
Linked BF Score: 13

 Description   

In SERVER-39484, to support rolling back two phased index builds, we started aborting index builds in IndexBuildsCoordinator::onRollback(). Unfortunately, this has the undesirable side effect of failing single phased index builds prematurely, leading to tests crashing in our CI system. To retain the original behavior for single phased index builds introduced in SERVER-30818, we should allow single phased index builds to run to completion.



 Comments   
Comment by Githook User [ 22/Jan/20 ]

Author:

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

Message: SERVER-45174 do not abort single phased index builds on rollback
Branch: master
https://github.com/mongodb/mongo/commit/5454740bad41bec94bf58918288d67f26638d986

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