We have had some issues where the master was not re electing after a node reboot.
Our config is a bit customised to say the list but we have automatic failover disabled and also the master and slaves are set from the config.
What can we do in cases like this when the master does not re elect itself after a reboot ? is there a line command to run to see the state and why the master is not coming back on. No master means limited functionality on the VM side ?
i would have expected that if the master is set as master as long as it comes back up, after a reboot, it should re elect itself ?
thanks
nodeweaver version 10.3.1
