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

rollback_after_enabling_majority_reads.js test should make sure the final rollback occurs on node 0

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 4.1.11
    • Fix Version/s: 4.2.1, 4.3.1
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.2
    • 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

      Description

      The rollback_after_enabling_majority_reads.js test runs a final rollback here after restarting node 0 with EMRC=true. It intends for the rollback to occur on node 0, but since node 0 is a SECONDARY at the time it is restarted with EMRC=true, the RollbackTest fixture will end up running the rollback on node 1. We should consider shutting down and restarting node 1 to let node 0 become primary again before initiating the final rollback sequence.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: