Handle fsync and fsyncUnlock during tenant migrations

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      fsync flushes all pending writes to disk, and if "lock: true" is specified, blocks the entire mongod from accepting writes (not just a particular database or collection).

      fsyncUnlock allows the mongod to start accepting writes again.

      I don't think we need to synchronize these with tenant migrations, since they don't change the user's data.

            Assignee:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: