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

Consider adding a server parameter that prevents secondaries from serving reads if they are too far behind

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • Repl 2024-12-23, Repl 2025-01-06, Repl 2025-01-20, Repl 2025-02-03, Repl 2025-02-17, Repl 2025-03-03, Repl 2025-03-17

      In HELP-66561, a bad rolling index build procedure caused read query delays due to a secondary being lagged. While there is a workaround that prevents it, a server parameter might be helpful in lieu of a particular process.

      This ticket is to consider whether or not this is a good idea and to document why or why not.

            Assignee:
            matt.panton@mongodb.com Matt Panton
            Reporter:
            brad.cater@mongodb.com Brad Cater
            Votes:
            0 Vote for this issue
            Watchers:
            20 Start watching this issue

              Created:
              Updated: