[SERVER-4935] Mark node Recovering when replication lag exceeds a configured threshold Created: 12/Feb/12 Updated: 06/Dec/22 Resolved: 11/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.0.2, 2.2.3 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 20 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||
| 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 Andy Schwerin [ 11/Jul/16 ] |
|
Closed in favor of |
| Comment by Vincent [ 24/Feb/14 ] |
|
This would be great, but I though I could be better on a per query basis: https://jira.mongodb.org/browse/SERVER-12861 |
| Comment by Eliot Horowitz (Inactive) [ 29/Mar/12 ] |
|
@idris - definitely similar, but different in fundamental ways. |
| Comment by Idris Mokhtarzada [ 28/Mar/12 ] |
|
This sounds pretty similar to |