It would be easier to give you an answer if you provide the
CIBs as attachment - specially in the state where you do not
understand why something happens ;-)
Here a couple things what comes me in mind.
* i have no clue if colocation rules work on Cloned resources as you
intended. The question is: if a clone primitive failes on one node,
what impact does it have on the score for the clone ("database"
or "webserver")?
* there is a nice tool called ptest from which you can get a lot of
info (toke me quite a while until i was able to work with it).
Here some filters i do when i debug a cluster:
/usr/lib/heartbeat/ptest -L -VVVVVVVV 2>&1|grep test_expression|less
/usr/lib/heartbeat/ptest -L -VVVVVVVV 2>&1|grep native_rsc_location|less
/usr/lib/heartbeat/ptest -L -VVVVVVVV 2>&1|grep resource_node_score|less
* there are in general two ways to work with colocation:
a) resources can not run anywhere except i tell them thay may run on a certain
node
b) resource can run evereywhere except i tell them to not run there.
(i forgot the CIB attruibute which manages this behaviour but if you read the
DTD it should be explained there)
---> this has an impact when your depeneding resource fail over
hope this helped a bit
kind regards Max
On Friday 15 June 2007, Christian Rishøj wrote:
> I have two servers in a master/master setup running MySQL, Lighttpd
> and DBRD/OCFS2. Each has a virtual public IP which is used to serve
> requests on the webserver:
>
> Node: ska (e9f7c85b-52f4-4aa8-8227-83e167e625bd): online
> Node: dub (807e97ee-cba3-400f-9d78-44e7d3d1820b): online
>
> Clone Set: webserver
> lighttpd:0 (lsb:lighttpd): Started dub
> lighttpd:1 (lsb:lighttpd): Started ska
> Clone Set: database
> MySQL:0 (heartbeat::ocf:mysql): Started dub
> MySQL:1 (heartbeat::ocf:mysql): Started ska
> dubWebIP (heartbeat::ocf:IPaddr): Started dub
> skaWebIP (heartbeat::ocf:IPaddr): Started ska
>
> The cluster is configured to be symmetric. I would like Heartbeat to:
>
> 1. Only start the WebIP resources on nodes where the database and
> webserver is started
> 2. Failover WebIP resources in case either the database or webserver fail
>
> Thus I have the following constraints:
>
> <rsc_colocation id="skaWebIP_webserver_colocation" from="webserver"
> to="skaWebIP" score="INFINITY"/>
> <rsc_colocation id="dubWebIP_webserver_colocation" from="webserver"
> to="dubWebIP" score="INFINITY"/>
> <rsc_colocation id="skaWebIP_database_colocation" from="database"
> to="skaWebIP" score="INFINITY"/>
> <rsc_colocation id="dubWebIP_database_colocation" from="database"
> to="dubWebIP" score="INFINITY"/>
>
> While this seems to ensure that WebIP resources are only started after
> the webserver and database, it does not seem to make the WebIP
> resources failover.
>
> What constraint am I missing?
>
> Best regards,
> Christian
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
--
Max Hofer
APUS Software G.m.b.H.
A-8074 Raaba, Bahnhofstraße 1/1
T| +43 316 401629 11
F| +43 316 401629 9
W| www.apus.co.at
E| [EMAIL PROTECTED]
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
