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

rollback_after_enabling_majority_reads.js test should ensure the correct primary before restarting other nodes [v4.0]

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 4.0.9
    • Fix Version/s: 4.0.13
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Repl 2019-06-17, Repl 2019-07-01, Repl 2019-07-15, Repl 2019-07-29, Repl 2019-08-12, Repl 2019-08-26, Repl 2019-09-09
    • Linked BF Score:
      43

      Description

      The rollback_after_enabling_majority_reads.js test expects node 0 to become primary here, by shutting down and restarting node 1. This may not always work if node 1 restarts and wins an election too soon. We should make this test wait for node 0 to become primary in this case before node 1 is restarted or is allowed to get elected.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: