[Linux-cluster] Unwanted cluster automigration after first node joins cluster

Lon Hohberger lhh at redhat.com
Tue Jul 12 13:50:20 UTC 2005

On Mon, 2005-07-11 at 18:55 +0200, Miroslav Zubcic wrote:
> I have another problem with Red Hat Cluster Suite:
> Let's say one (active) node in 2-node cluster failed. It is rebooted
> fenced etc... and services are migrated on the second node. That's OK.
> But when I repair and boot again first (previously failed) node and
> start cluster daemons with /etc/init.d/clumanager, services are
> MIGRATED BACK again (!!!) automaticly, couple of seconds after firing
> up first node.
> Since I have equal hardware for all nodes in cluster, and REALLY
> critical services, I'm experiencing unneeded service failover.
> How can I configure RH CS *NOT* to failover services back on the first
> node after first node is up again?

Don't use failover domains.

-- Lon

More information about the Linux-cluster mailing list