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

quiesce_mode.js does not properly wait for the proper find command to be established before entering quiesce mode

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.7.0
    • Affects Version/s: 4.5 Required
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2020-08-24, Repl 2020-09-07
    • 14

      Although we call findCmdFailPoint.wait(), this doesn't really help because wait() will only wait for the failpoint block to be entered once more from any command. The way the failpoint is defined, we will increment the timesEntered field for the failpoint on every find command while the failpoint is enabled. However, we will only hang the operation if the read is applied on the namespace that we pass in. Therefore, calling wait() will not guarantee that we have actually created the hanging operation that we care about on the primary.

            Assignee:
            jason.chan@mongodb.com Jason Chan
            Reporter:
            jason.chan@mongodb.com Jason Chan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: