Waiting for failpoint does not always throw in quiesce_mode.js

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.7.0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Repl 2020-08-24, Repl 2020-09-07
    • 35
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In quiesce_mode.js, when we wait for the pauseWhileKillingOperationsAtShutdown here and here, we assume that the waitForFailPoint command will be killed by the server, since the server has started killing new operations and marked all existing operations as killed. However, if the waitForFailPoint command was an existing operation, then even though it was marked as killed, it might not have any remaining interrupt points and could complete successfully.

            Assignee:
            Tess Avitabile (Inactive)
            Reporter:
            Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: