[SERVER-15157] Controlled primary step-down with no loss of write availability Created: 05/Sep/14  Updated: 06/Dec/22

Status: Open
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: Needs Further Definition

Type: Improvement Priority: Major - P3
Reporter: James Wahlin Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Replication
Participants:
Case:

 Description   

Stepping down a primary, to allow another replica member to become primary, incurs a brief period where no writes can be accepted. This can lead to application errors when not handled correctly and is a deterrent for some when considering machine maintenance or database upgrade.

Please allow for a controlled step down where there is no loss of write availability.


Generated at Thu Feb 08 03:37:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.