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

JournalFlusher can interrupt write concern with ShutdownInProgress during rollback

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.7.0, 4.4.2
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • None
    • Fully Compatible
    • v4.4
    • Execution Team 2020-09-07
    • 11

      This is both a problem because write_concern_after_stepdown.js expects a stepdown error code, and because it is semantically the wrong error code. Write concern waiting calls StorageControl::waitForJournalFlush(opCtx);. This does not have an interrupt point, though it will throw when the catalog is shutdown. We should either tell it what error code to throw when we shut down the catalog or make it interruptible.

            Assignee:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: