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

minValid should alway be set to existent OpTime

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.6.0-rc2
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v3.4
    • Repl 2017-11-13
    • 0

    Description

      We use a $max to update the minvalid which updates the timestamp and term independently: https://github.com/mongodb/mongo/blob/2197cedd9cc61cba6ceb81affc348d3e3932c1b8/src/mongo/db/repl/replication_consistency_markers_impl.cpp#L188-L192.

      If we provide a timestamp that is greater than the current minValid, but a term that is less, we can end up with a minValid that never existed. This occurs primarily on protocol version downgrade and can lead to us being unable to choose a sync source.

      Attachments

        Issue Links

          Activity

            People

              siyuan.zhou@mongodb.com Siyuan Zhou
              judah.schvimer@mongodb.com Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: