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

Move configureFailpoint to replica set startup in read_committed_no_snapshots.js

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.0-rc0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2018-04-09, Repl 2018-04-23, Repl 2018-05-07, Repl 2018-05-21
    • 46

      It is currently possible that the no-snapshot secondary actually does manage to take a snapshot in between when the primary is elected and when the failpoint is triggered. We should have it start with the failpoint already turned on instead.

            Assignee:
            vesselina.ratcheva@mongodb.com Vesselina Ratcheva (Inactive)
            Reporter:
            vesselina.ratcheva@mongodb.com Vesselina Ratcheva (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: