[SERVER-62172] Fix failure to handle stepDown within IndexBuildsCoordinator::createIndex Created: 17/Dec/21  Updated: 17/Mar/22  Resolved: 17/Mar/22

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

Type: Bug Priority: Major - P3
Reporter: Didier Nadeau Assignee: Suganthi Mani
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-57432 Prevent MODE_X and MODE_S locks from ... Closed
Related
Operating System: ALL
Steps To Reproduce:

See BF for reproduction steps.

Sprint: Server Serverless 2022-01-10, Server Serverless 2022-01-24, Server Serverless 2022-02-07, Server Serverless 2022-02-21, Server Serverless 2022-03-07, Server Serverless 2022-03-21
Participants:
Linked BF Score: 38

 Description   

When a stepdown occurs during index creation, the stepdown error can be improperly handled leading to an invariant failure and a crash of mongod.

See BF for more details and reproduction steps.



 Comments   
Comment by Suganthi Mani [ 17/Mar/22 ]

This problem no longer exists as it is fixed by this commit which makes sure that the foreground index builds don't yield locks. To be noted the problem mentioned in this ticket exists only for foreground index building.

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