FSyncLockThread::run() should not hold a lock while calling waitUntilDurable()

XMLWordPrintableJSON

    • Fully Compatible
    • Execution Team 2019-09-09, Execution Team 2019-09-23, Execution Team 2019-10-07
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The GlobalRead lock is acquired in fsync.

      However, we only call waitUntilDurable() if _allowFsyncFailure is set. _allowFsyncFailure is only set if getTestCommandsEnabled() and the "allowFsyncFailure" flag was set on the cmd request, which was added to make fsync+lock block writes against the server regardless of fsync success. That was added in this commit for the backup work.

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

              Created:
              Updated:
              Resolved: