[SERVER-14251] Change shutdown/stepdown to block writes and wait until at least 1 electable secondary is fully caught up Created: 13/Jun/14 Updated: 03/Mar/15 Resolved: 27/Oct/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.7.8 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
Currently shutdown starts by waiting for at least 1 secondary to be within 10 seconds of its optime (while still accepting new writes), then it steps down, then it waits again for a secondary to be completely caught up before shutting down. Once the new concurrency system allows it, we should start by blocking new incoming writes while retaining PRIMARY status, and wait until a secondary is completely caught up before stepping down and then shutting down. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 27/Oct/14 ] |
|
This was completed already when stepDown was implemented in the new replication coordinator |