Right.
Failure timeout is only evaluated on the next pengine run,
so if nothing else happens, it takes up to recheck-interval ...
Good to know.
had to set failure-timeout to the same value (failure-timeout="5m").
You should set it smaller than the recheck interval, I think.
Or you may need t
On Tue, Oct 15, 2013 at 11:28:14PM +0200, Robert H. wrote:
> Hi,
>
> I finally got it working.
>
> I had to set cluster-recheck-interval="5m" or some other value and
Right.
Failure timeout is only evaluated on the next pengine run,
so if nothing else happens, it takes up to recheck-interval ...
Hi,
I finally got it working.
I had to set cluster-recheck-interval="5m" or some other value and had
to set failure-timeout to the same value (failure-timeout="5m"). This
causes a "probe" after 5 minutes and then the cluster shows the correct
state and reevaluates the engine.
So the very st
Hi,
one more note:
When I cleanup the ressource, the monitor operation is triggered and
the result is as expected:
[root@NODE2 ~]# crm_resource --resource mysql-percona --cleanup --node
NODE2
Cleaning up mysql-percona:0 on NODE2
Waiting for 1 replies from the CRMd. OK
Clone Set: CLONE-per
You probably also want to monitor even if pacemaker thinks this is
supposed to be stopped.
op monitor interval=11s timeout=20s role=Stopped
I added this:
primitive mysql-percona lsb:mysql \
op start enabled="false" interval="0" \
op stop enabled="false" interval="0" \
Am 12.10.2013 01:53, schrieb Lars Ellenberg:
> On Thu, Oct 10, 2013 at 06:20:54PM +0200, Robert H. wrote:
>> primitive mysql-percona lsb:mysql \
>> op start enabled="false" interval="0" \
>> op stop enabled="false" interval="0" \
>> op monitor enabled="true" timeout="20s" in
On Thu, Oct 10, 2013 at 06:20:54PM +0200, Robert H. wrote:
> Hello,
>
> Am 10.10.2013 16:18, schrieb Andreas Kurz:
>
> >You configured a monitor operation for this unmanaged resource?
>
> Yes, and some parts work as expected, however some behaviour is
> strange.
>
> Config (relevant part only):
Hello Andreas,
Have you verified the mysql script is LSB compliant?
http://goo.gl/UqoHbv
[root@NODE2 ~]# /etc/init.d/mysql status; echo $?
MySQL (Percona XtraDB Cluster) running (10562) [ OK ]
0
[root@NODE2 ~]# /etc/init.d/mysql stop; echo $?
Shutting down MySQL (Percona Xtr
On 2013-10-10 18:20, Robert H. wrote:
> Hello,
>
> Am 10.10.2013 16:18, schrieb Andreas Kurz:
>
>> You configured a monitor operation for this unmanaged resource?
>
> Yes, and some parts work as expected, however some behaviour is strange.
>
> Config (relevant part only):
>
Hello,
Am 10.10.2013 16:18, schrieb Andreas Kurz:
You configured a monitor operation for this unmanaged resource?
Yes, and some parts work as expected, however some behaviour is
strange.
Config (relevant part only):
primitive mysql-percona lsb:mysql \
On 2013-10-09 18:33, Robert H. wrote:
> Hello list,
>
> I have a question regarding colocation.
>
> I have an external managed resource (not part of pacemaker, but running
> on the pacemaker nodes as multi master application) - in this case
> XtraDB Cluster. I also want to keep this ressource man
11 matches
Mail list logo