Update _setStableTimestampForStorage to set the stable timestamp without using the stable optime candidates set when EMRC=false

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.7.0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2020-07-13
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We want to set the stable timestamp when enableMajorityReadConcern:false without reliance on the stable optime candidates list. This should continue the work of SERVER-47844. We will not remove any of the logic for computing and updating the stable optime candidates set as a part of this ticket.

            Assignee:
            Will Schultz
            Reporter:
            Will Schultz
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: