Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-1941

Sync the journal directory, not its parent

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • WT2.6.1
    • Affects Version/s: None
    • Component/s: None
    • Labels:

      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.

            Unassigned Unassigned
            michael.cahill@mongodb.com Michael Cahill (Inactive)
            0 Vote for this issue
            5 Start watching this issue