[DOCS-9568] Docs for SERVER-4935: Mark node Recovering when replication lag exceeds a configured threshold Created: 05/Dec/16  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Emily Hall Assignee: Kay Kim (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-4935 Mark node Recovering when replication... Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

Engineering Ticket 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.



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Generated at Thu Feb 08 07:58:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.