[SERVER-39585] Explore whether index build failpoint 'crashAfterStartingIndexBuild' requires dropping locks to wait for durability Created: 14/Feb/19  Updated: 29/Oct/23  Resolved: 19/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

Issue Links:
Depends
is depended on by SERVER-39454 Move createIndexes command fully onto... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2019-02-25
Participants:

 Description   

saveLockStateAndUnlock cannot be successful under nested locking, which index builders can be called under. The failpoint crashAfterStartingIndexBuild is therefore brittle. I'm not aware of a reason requiring dropping locks to call RecoveryUnit::waitUntilDurable().



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

Author:

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

Message: SERVER-39585 do not drop index build locks in crashAfterStartingIndexBuild failpoint
Branch: master
https://github.com/mongodb/mongo/commit/c0aab8d201068303455e5c788afcc61444024594

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