On Monday 09 March 2009 03:28:11 pm Lars Marowsky-Bree wrote: > On 2009-03-05T16:02:02, Sebastian Reitenbach <[email protected]> wrote: > > Hi, > > > > I experienced some problems with Xen resources. > > > > I have a 4 node cluster, running 14 Xen domU's. > > Sounds good. > > > To not have a race condition on startup, when e.g. one node comes back > > from standby, or one node dies, I had to add order constraints for each > > domU, > > > > e.g. domU1 before domU2 > > domU1 before domU3 > > domU1 before domU4 > > Which race condition is this supposed to avoid ...? One internal to Xen, > or in your DomU work-load? When using automatic memory management, and then starting some domU's in parallel on the same node, due to the fact how they check for available memory, and that one Xen RA is not really aware of otheres, and what they are doing, it can happen that they overcommit memory.
> > > However, in the larger cluster, there the cluster is busy with itself, > > managing resources. E.g. the GUI seems to hang often, because of a too > > busy crmd. The cluster is busy with propagating updates of the cib, > > commands will time out.... > > That should NOT happen. Please file a bug. will do so. Sebastian > > > Regards, > Lars _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
