[SERVER-3027] configurable max secondary lag for primary stepdown Created: 30/Apr/11 Updated: 23/Feb/15 Resolved: 23/Feb/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Greg Studer | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
When manually stepping down a primary node in a replica set, it would be useful to have a configurable max secondary sync delay to ensure fast elections if needed. |
| Comments |
| Comment by Eric Milkie [ 23/Feb/15 ] |
|
The current behavior in 3.0 is that a secondary must be fully caught up for stepDown to succeed; there is a "force" option that will override this behavior. |
| Comment by Kristina Chodorow (Inactive) [ 07/May/11 ] |
|
In the latest version it's fixed at 10 seconds, but I can make it configurable. |