On Wed, Sep 15, 2010 at 10:04 AM, Tobias Appel <[email protected]> wrote: > Hi all, > > it's been some time since I last worked with Heartbeat. Now a workmate > asked me this question and hopefully I can get a short answer from you guys. > > The problem is that we use Xen on a Heartbeat cluster with a lot of > virtual machines. Now in certain cases there is a live migration of > virtual machines from one node to another. This works fine. The only > problem is that we don't know if we can limit the amount of resources > (virtual machines) that get migrated at the same time. > > If heartbeat tries to migrate all of the VM's at the same time, the RAM > will run full and some errors are being thrown resulting in the resource > going into an unmanaged state. > > So I just need to know if there is an option, or constraint to limit the > migration of resources from one node to another. > > We are still using Heartbeat 2.14
my eyes my eyes! :-) > or something like this, so it would > also be good to know if the (possible) option is only included in pacemaker. It's possible in pacemaker 1.1, but not very well documented. Basically you create an ordered set and set kind=Serialize > If nothing of that sort is available I will do further research on the > issue. > > Thanks in advance. > > Tobi > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
