Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13401

MongoDB's fsync command's 'async' field is inactive (does nothing) in MongoDB v4.2 and onward

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: manual

      Description

      Description

      Eric realized in the CR of SERVER-46067 that we do not do anything with the 'async' field in the WiredTiger implementation. In v4.2, the fsync command parses the 'async' field value here, passes the setting into StorageEngine::flushAllFiles, which the WT function implementation then does not use, as seen here.

      Master (v4.3) is the same code. SERVER-46067 will remove the inactive field in master, but the 'async' field has done nothing since v4.2. We suspect 'async' was only ever used for MMAP.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kay.kim Kay Kim (Inactive)
              Reporter:
              dianna.hohensee Dianna Hohensee
              Participants:
              Last commenter:
              Kay Kim Kay Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Due:
                Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 24 weeks, 3 days ago
                Date of 1st Reply: