Reputation: 323
I'm running a test keepalived cluster with two nodes, using the nopreempt
option. This allows me to prevent automatic failback to the Primary node after a crash. That configuration is working fine.
Therefore, I'm looking for an elegant way to trigger a manual failback once I ensured that the Primary node is healthy.
I already have found two solutions, but I don't consider them as elegant :
keepalived
service on the Secondary NodeI was hoping to find a way to "move" the cluster ressources manually without having to stop the keepalived
service.
I believe this option is good for tests, but not for production.
Do you know a better way to trigger a failover on a keepalived cluster ?
Thanks !
Upvotes: 0
Views: 9427
Reputation: 3909
How about increasing it's priority to a level you're certain it's the highest of the cluster. Followed by a service keepalived reload
?
Upvotes: 3