Lars,
The issue described was on a debian etch system. Nevertheless it's good to make
this script very failsafe. Adding a third node could (and did in our case)
result in a complete 'drop dead' of the configured resources on the first two
nodes.
See the philosophical node of Spaans's post.
Regards,
Gerard.
Lars Marowsky-Bree wrote:
On 2008-07-24T16:29:54, Gerard Petersen <[EMAIL PROTECTED]> wrote:
The third node is already added to heartbeat config, and in standby mode.
We have contraints in place (full log and config will follow), that work
with the +INF, 'zero' and -INF values, respectively as Master location,
Slave location and 'Never' location constraints.
When we take the third node online, where the current XenU's according to
the constraints are not allowed, the resources somehow all are moved to
the third node, where no xen or drbd is present yet. It seems some of the
constraints are completely ignored. We have tried this, among other
things, with the symmetric_cluster value True and False, but no luck.
The problem was that the Xen RA did not actually verify whether the "xm"
command was present, causing misbehaviour.
This is fixed with the RA from dev now.
Regards,
Lars
--
urls = { 'fun': 'www.zonderbroodje.nl', 'tech': 'www.gp-net.nl' }
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
