FsyncLock on WT should not imply "snapshotting" is OK

XMLWordPrintableJSON

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

      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 (Inactive)
            Reporter:
            Osmar Olivo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: