Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-76131

Move the global fsync state from the FSyncCommand to the FSyncLockThread

XMLWordPrintableJSON

    • Storage Execution
    • Execution EMEA Team 2023-07-24, Execution EMEA Team 2023-08-07, Execution EMEA Team 2023-08-21, Execution EMEA Team 2023-09-04, Execution EMEA Team 2023-09-18

      Most of this state is cross command logic that is accessed in FSyncCommand, FSyncUnlockCommand and FSyncLockThread. SERVER-70444 will make the mutex around this state global, so that shutdown has access. This ticket should move the rest of the state into the FSyncLockThread, rather than FSyncLockThread and FSyncUnlockCommand continuing to access the state through the fsyncCmd instance – grep for fsyncCmd. around the code.

            Assignee:
            josef.ahmad@mongodb.com Josef Ahmad
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: