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

Oplog fetcher should not retry when a node is known to be down

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.0.0-rc0, 5.0.7
    • None
    • None
    • Fully Compatible
    • v5.0
    • Repl 2022-03-07, Repl 2022-03-21
    • 176

    Description

      In steady state oplog fetching, the oplog fetcher will retry (once by default) on the same node it is already syncing from. If we already know the node is down (due to missed heartbeats), we should instead fail and re-run sync source selection. This will result in a shorter time to majority write availability in the case where the retry takes a long time.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-64635 Coverity analysis defect 121898: Parse warning

          • Trivial - P5 - Cosmetic problem like misspelt words or misaligned text.
          • Closed
          related to

          Task - A task that needs to be done. SERVER-63792 Improve coverage of blackholing network requests

          • Major - P3 - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-63418 Oplog fetcher should abort if node goes down

          • Major - P3 - Major loss of function.
          • Backlog

          Activity

            People

              matthew.russotto@mongodb.com Matthew Russotto
              matthew.russotto@mongodb.com Matthew Russotto
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: