Hi, Andrew
About 15 seconds are the time taken in the whole device construction.
I think that it cannot receive the message from cib during device
construction since stonith-ng does not return to mainloop.
Jun 2 11:34:02 vm04 stonith-ng[4891]: info: init_cib_cache_cb:
Updating device list fr
On 2 Jun 2014, at 7:05 pm, Riccardo Murri wrote:
> Hi Andrew,
>
> thanks for your explanations. One more question:
>
> On 30 May 2014 02:38, Andrew Beekhof wrote:
>>
>> On 29 May 2014, at 9:19 pm, Riccardo Murri wrote:
>>
>>> - or rather does the `ping` RA trigger failure events when even
On 2 Jun 2014, at 3:05 pm, Yusuke Iida wrote:
> Hi, Andrew
>
> I use the newest of 1.1 brunches and am testing by eight sets of nodes.
>
> Although the problem was settled once,
> Now, the problem with which queue overflows between cib and stonithd
> has recurred.
>
> As an example, I paste t
On 2 Jun 2014, at 5:43 pm, K Mehta wrote:
> Andrew,
> Will you let me know if using the rule (assuming this rule works) pcs -f
> $CLUSTER_CREATE_LOG constraint location vha-$uuid rule score=-INFINITY
> \#uname ne vsanqa11 and \#uname ne vsanqa12 might help in resolving
> unexpected demote ?
Hi,
On Fri, May 30, 2014 at 12:17:00PM +0100, Stuart Taylor wrote:
> Hi
>
> I wonder if anyone on the list can help me - I’m new to Pacemaker so
> apologies if I’m posting in the wrong place.
>
> I have a four-node cluster running Pacemaker 1.1.10 with Corosync 1.4.1 on
> CentOS 6.4. Resource
Hi Andrew,
thanks for your explanations. One more question:
On 30 May 2014 02:38, Andrew Beekhof wrote:
>
> On 29 May 2014, at 9:19 pm, Riccardo Murri wrote:
>
>> - or rather does the `ping` RA trigger failure events when even one of
>> the nodes cannot be pinged?
>
> both. it always trigger
Andrew,
Will you let me know if using the rule (assuming this rule works) pcs -f
$CLUSTER_CREATE_LOG constraint location vha-$uuid rule score=-INFINITY
\#uname ne vsanqa11 and \#uname ne vsanqa12 might help in resolving
unexpected demote ?
Regards,
Kiran
On Fri, May 30, 2014 at 11:58 AM, K Meh
