On Wed, Dec 2, 2009 at 4:39 PM, Miriam Wiesner <[email protected]> wrote: > Andrew Beekhof wrote: >> On Tue, Dec 1, 2009 at 2:51 PM, Miriam Wiesner <[email protected]> wrote: >> >>> Hello there, >>> >>> I'm setting up a high-available Web-server with DRBD. >>> I'm using heartbeat-2 and DRBD v8. >>> >>> I have two nodes: www-ha1 (DC) & www-ha2 >>> >>> My services: >>> - IPaddr >>> - pingd >>> - stonith resource (my own script) >>> - apache2 >>> - drbd (resource: /dev/drbd0 ) >>> - filesystem >>> >>> After a bit configuration every resource worked fine, except the >>> DRBD-resource. It's starting always it's master instance (drbd:0) on >>> www-ha2 instead of the DC. >>> >> >> The location of the DC has no relevance to where resources are placed. >> The DC is an internal detail, it affects only who makes the decision, >> not which node should be promoted. >> > Ok, I thought, that would influence my apache-resource.... > Apache runs atm on the DC
Just a co-incidence. >, so I thought its web resources (drbd manages > /www/) should be on the same node...? Only if you specified a colocation constraint. http://www.clusterlabs.org/doc/pacemaker-explained/s-resource-colocation.html _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
