Add ability to chose the new primary node when you perform a test election
There's a "test failover" option, which shuts down the primary and forces an election. However, you have no control over which new primary will be elected (just the preferred region) which sometimes does not work as expected.
It would be really useful if you have the possibility to manually chose which node will be elected as the new primary.
![](https://secure.gravatar.com/avatar/fcecfd65e79520e001a1d24d7eec0c7d?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
-
William commented
Excellent feature request! The ability to specify the new primary is necessary for testing disaster recovery operations and how downstream applications will perform. Without the ability to specify the new primary, the aforementioned tests are influenced by 'random chance'. Even worse, if the downstream applications are impacted by the failover test (e.g. increased latency or degradation to the new primary), its another roll of the dice to fail back to the original region.