Explore whether index build failpoint 'crashAfterStartingIndexBuild' requires dropping locks to wait for durability

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.9
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Storage NYC 2019-02-25
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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().

            Assignee:
            Dianna Hohensee (Inactive)
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: