<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Juan Ramon Martin Blanco wrote: <blockquote cite="mid:8a5668960902031040n6ee99e61padacd78a1e040c80@mail.gmail.com" type="cite"> <div class="gmail_quote">On Tue, Feb 3, 2009 at 7:31 PM, Marcos David <<a moz-do-not-send="true" href="mailto:marcos.david@efacec.pt">marcos.david@efacec.pt</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi, I have a 4 node cluster using RHEL 5.3. I have 4 services which I want to spread trough the servers so I can have some load-balancing. Each server should run one of the services when they are enabled, but what is happening is that the services always start on the node from which I enabled them. My configuration is this: FailOverDomain1 -> includes node1 only, unrestricted, unordered FailOverDomain2 -> includes node2 only, unrestricted, unordered FailOverDomain3 -> includes node3 only, unrestricted, unordered FailOverDomain4 -> includes node4 only, unrestricted, unordered </blockquote> <div>Hi Marcos, >From the Red Hat documentation: A failover domain is a named subset of cluster members that are eligible to run a cluster service in the event of a system failure. A failover domain can have the following characteristics: <ul> <li> Unrestricted — Allows you to specify that a subset of members are preferred, but that a cluster service assigned to this domain can run on any available member. </li> <li> Restricted — Allows you to restrict the members that can run a particular cluster service. If none of the members in a restricted failover domain are available, the cluster service cannot be started (either manually or by the cluster software). </li> <li> Unordered — When a cluster service is assigned to an unordered failover domain, the member on which the cluster service runs is chosen from the available failover domain members with no priority ordering. </li> <li> Ordered — Allows you to specify a preference order among the members of a failover domain. The member at the top of the list is the most preferred, followed by the second member in the list, and so on. </li> </ul> By default, failover domains are unrestricted and unordered. Configure them as restricted Greetings, Juanra </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> service1 is allocated to FailOverDomain1 service2 is allocated to FailOverDomain2 service3 is allocated to FailOverDomain3 service4 is allocated to FailOverDomain4 when I execute: clusvcadm -e service1 clusvcadm -e service2 clusvcadm -e service3 clusvcadm -e service4 all the services start on the same node (the one where I executed the above commands) Shouldn't they start on the node in their respective failover domain? Am I doing something wrong? Thanks for the help. -- Linux-cluster mailing list <a moz-do-not-send="true" href="mailto:Linux-cluster@redhat.com">Linux-cluster@redhat.com</a> <a moz-do-not-send="true" href="https://www.redhat.com/mailman/listinfo/linux-cluster" target="_blank">https://www.redhat.com/mailman/listinfo/linux-cluster</a> </blockquote> </div> <pre wrap=""> <hr size="4" width="90%"> -- Linux-cluster mailing list <a class="moz-txt-link-abbreviated" href="mailto:Linux-cluster@redhat.com">Linux-cluster@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/linux-cluster">https://www.redhat.com/mailman/listinfo/linux-cluster</a></pre> </blockquote> Hi, I based my configuration on the redhat documention: <h5 id="head-22e3273a63b2604d546a32fbf2e8245959fa6d3d">Preferred node or preferred member:</h5> This is a notion which is no longer present in rgmanager. In older versions, the preferred node was the member designated to run a given service if the member is online. In most cases, it was used with the "Relocate on Preferred Node Boot" service option (as it was generally thought to be useless without!). In newer rgmanagers, we can emulate this behavior by specifying an unordered, unrestricted failover domain of exactly one member. There is no equivalent to the "Relocate on Preferred Node Boot" option in Cluster Manager 1.0.x. So it was supposed to work. Or is the restricted option necessary in my case? Greetings, Marcos David </body> </html>