On Tue, Apr 5, 2011 at 11:58 AM, Maxim Ianoglo <dot...@gmail.com> wrote: > Hello, > > I have four serves in a HA cluster: > NodeA > NodeB > NodeC > NodeD > > There are defined three groups of resources and one inline resource: > 1. group_storage ( NFS VIP, NFS Server, DRBD ) > 2. group_apache_www (Domains VIPs and Apache) > 3. group_nginx_www (Static files with nginx) > 4. inline_nfs_client ( NFS client ) > > (1) should run only on NodeC or NodeD. NodeC is preferable. NodeD for backup. > (2) should run on NodeC and NodeD. NodeD is preferable. NodeC for backup. > (3) should run on NodeC and NodeD. NodeC is preferable. NodeD for backup. > (4) should run on every node except for node on which (1) is located. > > I have following orders: > (2) depends on (1) and (4) > (3) depends on (1) and (4) > (4) depends on (1) > > Collocations: > (4) and (1) should not run on same node. > > The issue is that resource (4) chooses NodeC which is the default node for > (1), so (1) had to choose another node but NodeC, so it goes to NodeD. > How can I make resource (1) to choose it's node earlier that (4) and any > other resource ?
Swap the order resources are listed in the colocation constraint. _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
