[SERVER-39826] Add a new index build failpoint to leave indexes unfinished and replace uses of hangAfterStartingIndexBuildUnlocked missing an 'off' call Created: 25/Feb/19  Updated: 29/Oct/23  Resolved: 26/Feb/19

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2019-02-25, Storage NYC 2019-03-11
Participants:

 Description   

hangAfterStartingIndexBuildUnlocked is currently used to hang an index build on a secondary until shutdown in a couple JS tests. This works when run on a [repl-index-builder-X] thread because the process exits on shutdown and those threads stop being scheduled. The IndexBuildsCoordinator, however, will wait for threads to finish on shutdown, so this behavior will hang shutdown once we move builds onto the Coordinator.

So instead of hanging until shutdown, we will add a failpoint that will cleanly interrupt the index build without cleaning up its persisted memory, just like clean shutdown does normally when an active index build throws InterruptedAtShutdown.



 Comments   
Comment by Githook User [ 26/Feb/19 ]

Author:

{'name': 'Dianna Hohensee', 'username': 'DiannaHohensee', 'email': 'dianna.hohensee@10gen.com'}

Message: SERVER-39826 add a new 'leaveIndexBuildUnfinishedForShutdown' failpoint and replace a couple failpoint use cases that hang across shutdown
Branch: master
https://github.com/mongodb/mongo/commit/fa959b60b65dbe543dcbd6531690a4d93f305679

Generated at Thu Feb 08 04:53:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.