Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
Description
Description
In our description of fsyncLock we say that fsyncLock ensures "that the data files do not change", but I don't believe this is true: it only ensures that they don't change in a way that will corrupt a copy taken while the instance is fsyncLock'ed.
Scope of changes
Impact to Other Docs
- Establish definition for fsynclock with better examples of what it does/does not do
- Document and backport.
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
Attachments
Issue Links
- is related to
-
SERVER-37814 db.fsyncLock() do not prevent writes to database on a separate filesystem
-
- Closed
-