Core Server
  1. Core Server
  2. SERVER-4935

Mark node Recovering when replication lag exceeds a configured threshold

    Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major - P3 Major - P3
    • Resolution: Unresolved
    • Affects Version/s: 2.0.2, 2.2.3
    • Fix Version/s: 2.7 Desired
    • Component/s: Replication/Pairing
    • Labels:
      None
    • Backport:
      No
    • Backward Breaking:
      Rarely
    • # Replies:
      3
    • Last comment by Customer:
      true
    • Documentation changes needed?:
      Yes
    • Driver changes needed?:
      No driver changes needed

      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.

        Issue Links

          Activity

          Hide
          Idris Mokhtarzada
          added a comment -

          This sounds pretty similar to SERVER-3346, though SERVER-3346 seems more like a setting on the driver.

          Show
          Idris Mokhtarzada
          added a comment - This sounds pretty similar to SERVER-3346 , though SERVER-3346 seems more like a setting on the driver.
          Hide
          Eliot Horowitz
          added a comment -

          @idris - definitely similar, but different in fundamental ways.
          this changes the state of the set
          the other is just a driver change that can be configured per request

          Show
          Eliot Horowitz
          added a comment - @idris - definitely similar, but different in fundamental ways. this changes the state of the set the other is just a driver change that can be configured per request
          Hide
          Vincent
          added a comment -

          This would be great, but I though I could be better on a per query basis: https://jira.mongodb.org/browse/SERVER-12861

          Show
          Vincent
          added a comment - This would be great, but I though I could be better on a per query basis: https://jira.mongodb.org/browse/SERVER-12861

            People

            • Votes:
              17 Vote for this issue
              Watchers:
              20 Start watching this issue

              Dates

              • Created:
                Updated:
                Days since reply:
                7 weeks, 6 days ago
                Date of 1st Reply: