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

Don't call for priority takeover when repl lagged

    XMLWordPrintableJSON

Details

    • Minor Change
    • Repl 2016-11-21

    Description

      Currently in pv1 we call for priority takeover without concern for whether the higher priority node is caught up in replication, which can lead to unnecessary rollbacks of w:1 writes. If we avoid calling for an election due to priority takeover if we are more than X seconds repl lagged, then that in combination with the catchup period should prevent any writes from being lost during priority takeover.

      Attachments

        Issue Links

          is documented by

          Task - A task that needs to be done. DOCS-9475 Docs for SERVER-26748: Don't call for priority takeover when repl lagged

          • Major - P3 - Major loss of function.
          • Backlog
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-26725 Automatically reconfig pv1 replica sets using priorities or arbiters to pv0

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-27056 Don't enforce data freshness for step-up command

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

          Activity

            People

              spencer@mongodb.com Spencer Brody (Inactive)
              spencer@mongodb.com Spencer Brody (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: