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

Remove support for 'fsync' flag in writeConcern specifications leftover from mmap

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Storage
    • None

    Description

      The 'fsync' flag in writeConcern is undocumented since mmap was removed. Eric managed to find this old documentation that mentions the fsync flag: https://docs.mongodb.com/v2.2/reference/command/getLastError/#dbcmd.getLastError. WT does still act on it, however.

      We still parse it from user writeConcern here and act on that flag in waiting for write concern here. flushAllFiles (that fsync flagged write concern calls) behaves differently in the WT integration layer code than a regular j:true flag: we explicitly take a checkpoint instead of flushing the journal.

      Attachments

        Activity

          People

            michael.gargiulo@mongodb.com Michael Gargiulo
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: