[SERVER-48143] Remove support for 'fsync' flag in writeConcern specifications leftover from mmap Created: 12/May/20  Updated: 14/Apr/22

Status: Open
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Michael Gargiulo
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-48144 waitUntilDurable should not take a mu... Closed
Participants:

 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.


Generated at Thu Feb 08 05:16:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.