[DOCS-10221] Primary failover time may be outdated: "manual/tutorial/upgrade-revision.txt" Created: 06/May/17 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jonathan Freeman | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | collector-298ba4e7, docs-triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: https://docs.mongodb.com/manual/tutorial/upgrade-revision/#upgrade-the-primary |
||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
The expected failover window stated in the documentation is 10-20 seconds, during which writes will not be expected. However, it appears that this figure may be outdated due to the enhancements to the replication protocol released in 3.2. The release notes (https://docs.mongodb.com/manual/release-notes/3.2/#replication-election-enhancements) say that the failover time is reduced, but don't mention by how much. Is the 10-20 second window still applicable? |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |
| Comment by Spencer Brody (Inactive) [ 08/May/17 ] |
|
The default election timeout in pv1 is 10 seconds, so I think saying 10-20 seconds still seems reasonable. People who have changed their election timeout in order to achieve faster failover will already know what to expect. |
| Comment by Jonathan Freeman [ 07/May/17 ] |
|