On Fri, Apr 20, 2012 at 12:30 AM, David Vossel wrote:
> - Original Message -
>> From: "Parshvi"
>> To: pacema...@clusterlabs.org
>> Sent: Thursday, April 19, 2012 6:22:01 AM
>> Subject: [Pacemaker] start/stop operations fail to happen in parallel on
- Original Message -
> From: "Parshvi"
> To: pacema...@clusterlabs.org
> Sent: Thursday, April 19, 2012 6:22:01 AM
> Subject: [Pacemaker] start/stop operations fail to happen in parallel on
> resources
>
> Observations:
> max-children=30
> t
Dan Frincu writes:
>
> Hi,
>
> > c. SOLUTION: the max-children of lrmd was raised to 30.
> > d. ISSUES STILL OBSERVED: while 2-3 resources are stuck in start operation,
> > if a rsc is issued an explicit start command `crm resource start rcs1`,
> > then
the
> > start op on this rsc is delay
Hi,
On Thu, Apr 19, 2012 at 2:22 PM, Parshvi wrote:
> Observations:
> max-children=30
> total no. of resources=18
>
> 1) At a default value 4 of max-children, following logs were observed
> that led to monitor op’s timeout for some resources (a total of 18 rscs):
> a. “max_child_count (4) reache
Observations:
max-children=30
total no. of resources=18
1) At a default value 4 of max-children, following logs were observed
that led to monitor op’s timeout for some resources (a total of 18 rscs):
a. “max_child_count (4) reached, postponing execution of operation monitor”
b. “WARN: perform
