On Thu, Apr 14, 2016, at 11:12 AM, Ken Gaillot wrote:
> On 04/14/2016 09:33 AM, Christopher Harvey wrote:
> > MsgBB-Active is a dummy resource that simply returns OCF_SUCCESS on
> > every operation and logs to a file.
>
> That's a common mistake, and will confuse the cluster. The cluster
> checks
Ken Gaillot wrote:
> On 04/14/2016 09:33 AM, Christopher Harvey wrote:
> > MsgBB-Active is a dummy resource that simply returns OCF_SUCCESS on
> > every operation and logs to a file.
>
> That's a common mistake, and will confuse the cluster. The cluster
> checks the status
On 04/14/2016 09:33 AM, Christopher Harvey wrote:
> MsgBB-Active is a dummy resource that simply returns OCF_SUCCESS on
> every operation and logs to a file.
That's a common mistake, and will confuse the cluster. The cluster
checks the status of resources both where they're supposed to be running
actually, toggling vmr-132-5 in the following simpler setup produces the
same service flap as before.
Cluster Name:
Corosync Nodes:
192.168.132.5 192.168.132.4 192.168.132.3
Pacemaker Nodes:
vmr-132-3 vmr-132-4 vmr-132-5
Resources:
Resource: MsgBB-Active (class=ocf provider=solace
On 04/13/2016 11:23 AM, Christopher Harvey wrote:
> I have a 3 node cluster (see the bottom of this email for 'pcs config'
> output) with 3 nodes. The MsgBB-Active and AD-Active service both flap
> whenever a node joins or leaves the cluster. I trigger the leave and
> join with a pacemaker service
I have a 3 node cluster (see the bottom of this email for 'pcs config'
output) with 3 nodes. The MsgBB-Active and AD-Active service both flap
whenever a node joins or leaves the cluster. I trigger the leave and
join with a pacemaker service start and stop on any node.
Here is the happy steady