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

Use stopOplogFetcher failpoint instead of rsSyncApplyStop failpoint in write_concern_after_stepdown_and_stepup.js

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.2, 3.5.2
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v3.4, v3.2
    • Platforms 2017-01-23
    • 0

      rsSyncApplyStop does not stop replication, it just stops applying buffered oplog entries. stopOplogFetcher actually stops replication

            Assignee:
            spencer.jackson@mongodb.com Spencer Jackson
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: