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

FsyncLock on WT should not imply "snapshotting" is OK

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.8.0-rc5
    • Component/s: Concurrency, Usability
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: