eekhof.net]
> Sent: Monday, February 17, 2014 6:46 PM
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] resource is too active problem in a 2-node cluster
>
> On 18 Feb 2014, at 5:33 am, Ajay Aggarwal wrote:
>
>> Thanks Andrew for pointing towards th
, 2014 6:46 PM
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] resource is too active problem in a 2-node cluster
On 18 Feb 2014, at 5:33 am, Ajay Aggarwal wrote:
> Thanks Andrew for pointing towards the OCF resource agent's list of "must
> implement" ac
On 18 Feb 2014, at 5:33 am, Ajay Aggarwal wrote:
> Thanks Andrew for pointing towards the OCF resource agent's list of "must
> implement" actions. I noticed that our OCF script only implements start, stop
> and monitor. It does not implement meta-data and validate-all. Could this
> error be
Thanks Andrew for pointing towards the OCF resource agent's list of
"must implement" actions. I noticed that our OCF script only implements
start, stop and monitor. It does not implement meta-data and
validate-all. Could this error be a result of these un-implemented
actions?
Thanks
On 02/1
On 12 Feb 2014, at 1:39 am, Ajay Aggarwal wrote:
> Yes, we have cman (version: cman-3.0.12.1-49). We use manual fencing ( I know
> it is not recommended). There is an external monitoring and fencing service
> that we use (our own).
>
> Perhaps subject line "resource is too active problem in
ted.
Ajay
From: Ajay Aggarwal [aaggar...@verizon.com]
Sent: Tuesday, February 11, 2014 9:39 AM
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] resource is too active problem in a 2-node cluster
Yes, we have cman (version: cman-3.0.12.1-49). We use manual fencing ( I
know
Yes, we have cman (version: cman-3.0.12.1-49). We use manual fencing ( I
know it is not recommended). There is an external monitoring and
fencing service that we use (our own).
Perhaps subject line "resource is too active problem in a 2-node
cluster" was misleading. Real problem is that resou
On 10/02/14 09:13 PM, Aggarwal, Ajay wrote:
I have a 2 node cluster with no-quorum-policy=ignore. I call these nodes as
node-0 and node-1. In addition, I have two cluster resources in a group; an
IP-address and an OCF script.
Turning off quorum on a 2-node cluster is fine, in fact, it's requi
I have a 2 node cluster with no-quorum-policy=ignore. I call these nodes as
node-0 and node-1. In addition, I have two cluster resources in a group; an
IP-address and an OCF script.
Normally these resources are active on node-0. However when I bounce pacemaker
on node-1 (service pacemaker stop
