[SERVER-11780] Secondary automatically enters Recovery if falls too far behind Created: 19/Nov/13 Updated: 19/Nov/13 Resolved: 19/Nov/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Charlie Page | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
When a secondary falls too far behind replicating (should be settable, probably at the replication set level), the secondary should automatically enter recovery mode until it catches up to prevent reads. This would help in situations were clients are reading off secondaries but cannot afford to read data that is too stale. |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 19/Nov/13 ] |
|
dup of |