SERVER-15157Open

Controlled primary step-down with no loss of write availability

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|http://docs.mongodb.org/manual/tutorial/force-member-to-be-primary/#force-a-member-to-be-primary-using-database-commands] where there is no loss of write availability.

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix
Needs Further Definition
Components
Server components related to this issue
Replication
Labels
Tags and classification

No labels assigned.