[DOCS-4328] Document revised stepdown behavior in new replication coordinator Created: 11/Nov/14 Updated: 16/Mar/15 Resolved: 26/Nov/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.14, mongodb-3.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Michael Paik | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 9 years, 12 weeks, 2 days ago | ||||||||||||||||
| Description |
|
stepDown command now waits for one secondary to be totally caught up, rather than just within 10 seconds of primary. This is to avoid rollbacks. (per https://jira.mongodb.org/browse/SERVER-14444?focusedCommentId=749739&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-749739) |
| Comments |
| Comment by Spencer Brody (Inactive) [ 24/Nov/14 ] |
|
Dup of |