-
Type: Improvement
-
Resolution: Done
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Admin, Replication
-
Replication
To elect a particular node as the primary, I have to go through a complicated process:
1. Connect to the existing primary.
2. Get the existing replica set configuration.
3. Set the priorities of each node in the set, with the desired new primary highest.
4. Set the new configuration.
It would be much easier if there were a single command "setPrimary(newPrimary)" or some such that would immediately elect the specified node as the primary, so long as that request was not contradicted by other configuration. In other words, in cases where multiple nodes are equally able to become primary based on their configurations, we should be able to determine which one actually gets elected.