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

Choose whether to do oplog catch up based on local last fetched optime rather than last applied optime

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None

    Description

      When a node decides if it's up to date, it compares the highest last applied optime of other nodes to it's own last applied optime: https://github.com/mongodb/mongo/blob/r3.4.2/src/mongo/db/repl/replication_coordinator_impl.cpp#L2781-L2788

      We could go into drain mode faster and skip catch up more often if nodes compared the highest last applied optime of other nodes to their own last fetched optime instead.

      Attachments

        Activity

          People

            judah.schvimer@mongodb.com Judah Schvimer
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: