Hi Ken,
> -Original Message-
> From: Ken Gaillot [mailto:kgail...@redhat.com]
> Sent: Tuesday, May 30, 2017 4:32 PM
> To: users@clusterlabs.org
> Subject: Re: [ClusterLabs] clearing failed actions
>
> On 05/30/2017 09:13 AM, Attila Megyeri wrote:
> > Hi,
> >
> >
> >
> > Shouldn't the
>
Hi.
I'm trying to setup a 2-node corosync+pacemaker cluster to function as an
active-active setup for nginx with a shared IP.
I've discovered (much to my disappointment) that every time I restart one
node or put it in standby, the second instance of the cloned IP gets moved
to the first node and
On 05/30/2017 09:13 AM, Attila Megyeri wrote:
> Hi,
>
>
>
> Shouldn’t the
>
>
>
> cluster-recheck-interval="2m"
>
>
>
> property instruct pacemaker to recheck the cluster every 2 minutes and
> clean the failcounts?
It instructs pacemaker to recalculate whether any actions need to be
Hi,
Shouldn't the
cluster-recheck-interval="2m"
property instruct pacemaker to recheck the cluster every 2 minutes and clean
the failcounts?
At the primitive level I also have a
migration-threshold="30" failure-timeout="2m"
but whenever I have a failure, it remains there forever.
What
Hello everybody,
I was switching from tgtd to lio as iscsi target and hitting some issues.
I have to manually run the targetcli command after the pacemaker
resources are started successfully:
/iscsi/iqn.20iscsi0/tpgt1> luns/ create /backstores/iblock/iscsi0_lun0
to get the mappings
