[SERVER-26747] replSetStepDown should wait for last write to commit Created: 24/Oct/16 Updated: 07/Mar/17 Resolved: 14/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.12, 3.4.0-rc4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | William Schultz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v3.2
|
||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Repl 2016-10-31, Repl 2016-11-21 | ||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Today, replSetStepDown waits for one node to have caught up completely with it. Instead, we can change this behavior to wait for a majority of nodes to catch up completely with it. |
| Comments |
| Comment by Githook User [ 29/Dec/16 ] |
|
Author: {u'username': u'will62794', u'name': u'William Schultz', u'email': u'william.schultz@mongodb.com'}Message: (cherry picked from commit 627f25d2e64078a6de32116aa496ffc3c461ec67) |
| Comment by William Schultz (Inactive) [ 14/Nov/16 ] |
|
Documentation changes: replSetStepDown previously required only one secondary to be caught up to the primary and electable before stepping down. Now it requires that a majority of nodes are caught up to the primary, and that at least one electable node exists among this majority. |
| Comment by Githook User [ 14/Nov/16 ] |
|
Author: {u'username': u'will62794', u'name': u'William Schultz', u'email': u'william.schultz@mongodb.com'}Message: |