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

Mark node Recovering when replication lag exceeds a configured threshold

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.0.2, 2.2.3
    • Component/s: Replication
    • None
    • Sharding
    • Minor Change

      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.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            scotthernandez Scott Hernandez (Inactive)
            Votes:
            20 Vote for this issue
            Watchers:
            28 Start watching this issue

              Created:
              Updated:
              Resolved: