Product SiteDocumentation Site

9.7. Test Failover

Testing failover is left as an exercise for the reader. For example, you can put one node into standby mode, use pcs status to confirm that its ClusterIP clone was moved to the other node, and use arping to verify that packets are not being lost from any source host.

Note

You may find that when a failed node rejoins the cluster, both ClusterIP clones stay on one node, due to the resource stickiness. While this works fine, it effectively eliminates load-balancing and returns the cluster to an active-passive setup again. You can avoid this by disabling stickiness for the IP address resource:
[root@pcmk-1 ~]# pcs resource meta ClusterIP resource-stickiness=0