[Pacemaker] (Linux-HA)resource-stickiness automatically move all resources in certain time

[Daniel Bozeman]

I believe it is preferable to bring failed nodes up manually. You'll want to investigate why the node failed exactly, resolve the issue if any, then bring the node up manually. Automatically bringing the node back up when it may be facing some random issue is ill-advised.

--Daniel

On Jun 8, 2011, at 10:10 AM, Warrior wrote:

> Hello, 
> I`ve configured heartbeat and pacemaker with 2 nodes, all resources work 
> well, all resources start when some of them is down, when the host is down, 
> pacemaker moves all resources to the other one, my configuration: 
> 
> node $id="06d57c5a-3d47-4ef1-b518-7b8501f5ca9d" premailman1.mpt.es 
> node $id="9af2ea3b-b7ad-458f-b7d0-2491b72db28f" premailman.mpt.es 
> primitive IP-Virtual ocf:heartbeat:IPaddr \ 
>     params ip="10.1.24.201" 
> primitive apache_mailman lsb:httpd \ 
>     op monitor interval="15" timeout="15" start-delay="15" \ 
>     meta target-role="Started" 
> primitive apache_webmail lsb:httpd \ 
>     op monitor interval="15" timeout="15" start-delay="15" \ 
>     meta target-role="Started" 
> primitive httpd_mailman ocf:heartbeat:anything \ 
>     params binfile="/usr/local/bin/httpd_mailman" 
> primitive httpd_webmail ocf:heartbeat:anything \ 
>     params binfile="/usr/local/bin/httpd_webmail" 
> primitive mailman ocf:heartbeat:anything \ 
>     params binfile="/var/mailman/bin/mailmanctl" cmdline_options="start" \ 
>     op start interval="0s" timeout="60s" on-fail="restart" \ 
>     op monitor interval="10s" timeout="60s" on-fail="restart" \ 
>     op stop interval="0s" timeout="60s" on-fail="block" 
> primitive smtp_postfix ocf:heartbeat:postfix \ 
>     params binary="/etc/init.d/postfix" \ 
>     op start interval="0s" timeout="60s" on-fail="restart" \ 
>     op monitor interval="10s" timeout="60s" on-fail="restart" \ 
>     op stop interval="0s" timeout="60s" on-fail="block" 
> colocation colocation-1 inf: IP-Virtual apache_mailman 
> colocation colocation-2 inf: IP-Virtual smtp_postfix 
> colocation colocation-3 inf: IP-Virtual mailman 
> colocation colocation-4 inf: IP-Virtual httpd_mailman 
> property $id="cib-bootstrap-options" \ 
>     dc-version="1.1.1-b9b672590e79770afb63b9b455400d92fb6b5d9e" \ 
>     cluster-infrastructure="Heartbeat" \ 
>     stonith-enabled="false" \ 
>     start-failure-is-fatal="false" \ 
>     no-quorum-policy="ignore" \ 
>     last-lrm-refresh="1306416533" 
> rsc_defaults $id="rsc-options" \ 
>     resource-stickiness="INFINITY" 
> 
> as I said everything works well, but i need just one thing, i have the 
> directive " resource-stickiness="INFINITY", when node1 is down, the node2 
> starts all resources and prevent  failback again though the node1 is up, 
>  back i need move all resources to the first one when I certainly sure the 
> node1 is runnig, is there some directive to tell pacemaker that move back 
> again the to node1 automatically? i mean, is posibble to move back resources 
> to node1 when It has passed certain time, maybe 1 hour or something? _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110608/cd9f2677/attachment-0003.html>