On 04/09/2013, at 1:01 AM, Matthew O'Connor wrote:
>
> On 08/27/2013 06:18 PM, Andrew Beekhof wrote:
> > Are you aware of this cluster
> option?
>
>
> >
>
>
> >batch-limit = integer [30]
>
>
> >The number of jobs that the TE is allowed to
>
On 08/27/2013 06:18 PM, Andrew Beekhof wrote:
> Are you aware of this cluster option?
>
>batch-limit = integer [30]
>The number of jobs that the TE is allowed to execute in
parallel
>
>The "correct" value will depend on the speed and load of
your network and cluster
On 2013-08-28T08:18:48, Andrew Beekhof wrote:
> > 4. once pacemaker has brought the node online, all vm resource are
> > started one at a time (for X...; crm resource start $X; sleep 45s; done)
>
> Are you aware of this cluster option?
>
>batch-limit = integer [30]
>The numb
On 28/08/2013, at 12:20 AM, Matthew O'Connor wrote:
> Hi!
>
> I have a server that operates about 30 virtual machines. Normally it
> handles this load very well, but restart can be a bit dicey. I have
> found that by staggering the vm startups - currently done manually - the
> system handles
Hi!
I have a server that operates about 30 virtual machines. Normally it
handles this load very well, but restart can be a bit dicey. I have
found that by staggering the vm startups - currently done manually - the
system handles the growing load much more gracefully. The sequence goes
something
