Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-16565

FsyncLock on WT should not imply "snapshotting" is OK

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • 2.8.0-rc5
    • Affects Version/s: None
    • Component/s: Concurrency, Usability
    • None
    • Fully Compatible

      When WiredTiger is the active storage engine, db.fsyncLock() does not completely quiesce the database. Writes may still occur in the background.

      We should not imply that the database is locked "for snapshotting" in this state.

            Assignee:
            matt.kangas Matt Kangas
            Reporter:
            osmar.olivo Osmar Olivo
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: