Remove obsolete code related to storing and updating stable optime candidates

XMLWordPrintableJSON

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

      Once we set the stable timestamp for storage without dependence on the stable optime candidates set, we can remove any obsolete/dead code related to storing and updating this set.

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

                Created:
                Updated:
                Resolved: