-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
From bruce.lucas@10gen.com in SERVER-18314:
Why are we periodically fdatasyncing the dbpath directory, asynchronously wrt the ongoing checkpoint, on a thread which apparently completely blocks things if it gets blocked, but only it seems if the journal is enabled? Theory: the journaling code does an fdatasync on the journal directory whenever it creates a new file to ensure durability of that directory entry; perhaps this code is incorrecly fdatasyncing the dbpath directory instead of the journal directory. As corroborating evidence, I tried doing an strace and couldn't see any evidence that we ever opened the journal directory, so it seems we couldn't be fdatasyncing it. Will continue investigating and open SERVER ticket if appropriate.
- is depended on by
-
SERVER-18629 WiredTiger journal system syncs wrong directory
- Closed
-
SERVER-18314 Stall during fdatasync phase of checkpoints under WiredTiger and EXT4
- Closed
-
SERVER-18647 WiredTiger changes for MongoDB 3.0.4
- Closed
-
SERVER-18648 WiredTiger changes for MongoDB 3.1.4
- Closed