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

JournalFlusher can interrupt write concern with ShutdownInProgress during rollback

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.7.0, 4.4.2
    • Component/s: Replication, Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.4
    • Sprint:
      Execution Team 2020-09-07
    • Linked BF Score:
      11

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: