[SERVER-77083] Index build stepUp async task should tolerate stepdowns Created: 12/May/23  Updated: 29/Oct/23  Resolved: 18/May/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 7.0.0-rc2

Type: Bug Priority: Major - P3
Reporter: Josef Ahmad Assignee: Josef Ahmad
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.0
Sprint: Execution Team 2023-05-15, Execution Team 2023-05-29
Participants:
Linked BF Score: 135

 Description   

On step-up, mongod checks if the commit quorum is satisfied on each active index build. As of SERVER-73331, that check runs in an async task which is killable on stepdown. We should handle the stepdown instead of fasserting.



 Comments   
Comment by Githook User [ 19/May/23 ]

Author:

{'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}

Message: SERVER-77083 Index build stepup async task should tolerate stepdowns

(cherry picked from commit https://github.com/10gen/mongo/commit/846ed8250b4c3322e52c2e51c4a6992c6ce7ba34)

This cherry-pick also marks the stepup async task as killable by stepdown,
because this revision predates SERVER-70127 which defaults system operations
to be killable by stepdown.

Conflicts:
src/mongo/db/index_builds_coordinator.cpp
Branch: v7.0
https://github.com/mongodb/mongo/commit/dee4cd988431e8753bde5929216a74400561ba19

Comment by Githook User [ 17/May/23 ]

Author:

{'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}

Message: SERVER-77083 Index build stepup async task should tolerate stepdowns
Branch: master
https://github.com/mongodb/mongo/commit/846ed8250b4c3322e52c2e51c4a6992c6ce7ba34

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