Details
-
Improvement
-
Resolution: Done
-
Minor - P4
-
None
-
None
-
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
- is documented by
-
DOCS-4652 Update fsync documentation to clarify that lock=true does not mean data is not in motion on WT
-
- Closed
-
- is related to
-
DOCS-4536 FSync+Lock does not work on WT
-
- Closed
-
- related to
-
SERVER-17557 Display warning when running db.fsyncLock() when running with WiredTiger
-
- Closed
-