[Linux-cluster] How to achieve a service's "stickyness" to a"preferred" node in RHCS?

[Santeramo Luc]

Hi,

        <failoverdomains>
            <failoverdomain name="FOD_srv1" nofailback="1" ordered="1" restricted="1">
                <failoverdomainnode name="srv1" priority="10"/>
                <failoverdomainnode name="srv2" priority="20"/>
            </failoverdomain>
            <failoverdomain name="FOD_srv2" nofailback="1" ordered="1" restricted="1">
                <failoverdomainnode name="srv1" priority="20"/>
                <failoverdomainnode name="srv2" priority="10"/>
            </failoverdomain>
        </failoverdomains>

<service autostart="1" domain="FOD_srv1" exclusive="0" name="SVC_001" recovery="relocate">
            <ip ref="10.100.0.8"/>
</service>

SVC_001 will be sticked to Failover Domain "FOD_srv1", which have node srv1 as priority node.

...and you can have more informations about options on RHCS admin guide.

Luc

________________________________

Le 24/06/2011 09:17, Ralph.Grothe at itdz-berlin.de<mailto:Ralph.Grothe at itdz-berlin.de> a écrit :

Hello Clustering Gurus,

I need to have a service during normal operation (i.e. not during
relocation when loss of stickyness is ok and wanted) stick to a
preferred cluster node.
(n.b. this is only a two-node cluster)

In the redhat cluster admin guide (we're on RHEL 5.6) I think to
have read that such thing as a "preffered_node" or similar
attribute doesn't exist in the schema any more and that instead
one should define ordered="0" and restricted="0" failover domains
for the respective service as this would in effect result in the
wanted behavior.

Is this correct?
And how (e.g. a short cluster.conf XML example snippet would be
appreciated) would this have to be applied?


Regards
Ralph

--
Linux-cluster mailing list
Linux-cluster at redhat.com<mailto:Linux-cluster at redhat.com>
https://www.redhat.com/mailman/listinfo/linux-cluster

**********************************************************************************************
Pensez a l'environnement avant d'imprimer ce message
Think Environment before printing
 
Le contenu de ce mel et de ses pieces jointes est destine a l'usage exclusif du (des) destinataire(s) designe
(s) comme tel(s). 
En cas de reception par erreur, le signaler a son expediteur et ne pas en divulguer le contenu. 
L'absence de virus a ete verifiee a l'emission, il convient neanmoins de s'assurer de l'absence de 
contamination a sa reception.
 
The contents of this email and any attachments are confidential. They are intended for the named recipient
(s) only. 
If you have received this email in error please notify the system manager or the sender immediately and do 
not disclose the contents to anyone or make copies. 
eSafe scanned this email for viruses, vandals and malicious content.
**********************************************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20110624/6e58ffca/attachment.htm>