[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: |
|
||||||||
| 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: |