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

Consider term and rbid when validating the proposed sync source

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Critical - P2 Critical - P2
    • 3.2.13, 3.4.4, 3.5.5
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v3.4, v3.2
    • Repl 2017-01-23, Repl 2017-02-13, Repl 2017-03-06, Repl 2017-03-27
    • 19

      When the document returned by the GTE query against our sync source does not include our most recent optime (ie the term and timestamp of our most recent oplog entry), we currently unconditionally return OplogStartMissing and go into ROLLBACK. The GTE query only includes the timestamp however, not the term, so we need to check the term and if the optime (including term) of our most recent oplog entry is higher than the optime we got back from the GTE query, we should not go into rollback but should just choose a new sync source.

            judah.schvimer@mongodb.com Judah Schvimer
            spencer@mongodb.com Spencer Brody (Inactive)
            0 Vote for this issue
            15 Start watching this issue