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

Mark node Recovering when replication lag exceeds a configured threshold

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • 2.0.2, 2.2.3
    • None
    • Replication
    • None
    • Sharding
    • Minor Change

    Description

      Add a replica set member option, or maybe a set-wide option, that when exceeded causes the member to change into Recovering mode. With a threshold like this it will be easier to make sure non-primary client reads never exceed the threshold/stale-ness when using a secondary preferred read preference.

      This essentially allows one to set the maximum staleness of any normally used member in replica set. This could also be used after maintenance periods to ensure that a node coming out of maintenance can catch up quickly without taking reads during the recovery period.

      Attachments

        Issue Links

          is documented by

          Task - A task that needs to be done. DOCS-9568 Docs for SERVER-4935: Mark node Recovering when replication lag exceeds a configured threshold

          • Major - P3 - Major loss of function.
          • Closed
          is duplicated by

          New Feature - A new feature of the product, which has yet to be developed. SERVER-9319 Allow to disable secondaries when they are behinded for a long time.

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

          New Feature - A new feature of the product, which has yet to be developed. SERVER-11780 Secondary automatically enters Recovery if falls too far behind

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-8476 slaveDelay with Ghostsync

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-4936 Server support for "maxStalenessMS" read preference option

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

          New Feature - A new feature of the product, which has yet to be developed. SERVER-12861 Introduce a maxStalenessMS option when querying secondaries

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-3346 MAX SLAVE LAG - Features to provide a more stable Replication Set under high load

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

          Activity

            People

              backlog-server-sharding Backlog - Sharding Team
              scotthernandez Scott Hernandez (Inactive)
              Votes:
              20 Vote for this issue
              Watchers:
              28 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: