Ulrich.Windl at rz
Aug 22, 2012, 12:00 AM
Post #1 of 7
(302 views)
Permalink
|
|
Antw: Duplicate monitor operation on a multi state resource
|
|
>>> RaSca <rasca [at] miamammausalinux> schrieb am 21.08.2012 um 18:05 in Nachricht
<5033B1C0.4010302 [at] miamammausalinux>:
> Hi all,
> I'm trying to use the mysql resource agent to manage a setup with one
> master and two slaves. This is the configuration of the mysql resource
> and the master/slave one:
>
> primitive resMySQL ocf:custom:mysql \
> params binary="/usr/bin/mysqld_safe" config="/etc/my.cnf"
> datadir="/var/lib/mysql" user="mysql" replication_user="myuser"
> replication_passwd="mypassword" \
> op start interval="0" timeout="120" \
> op stop interval="0" timeout="120" \
> op promote interval="0" timeout="120" \
> op demote interval="0" timeout="120" \
> op monitor interval="10" role="Master" timeout="30" \
> op monitor interval="10" role="Slave" timeout="30"
Hi!
Amazingly the "primary key" (=ID) of the monitor operations is built using the "ineterval", not the "role". So if you have to monitor operations with the same interval, you have a resource conflict. It's documented, although it's a sick concept...
Decide whose fault it is... yours or the CRMs...
Regards,
Ulrich
> ms ms_resMySQL resMySQL \
> meta master-max="1" master-node-max="1" clone-node-max="1"
> clone-max="3" notify="true" globally-unique="false"
>
> The problem is that I see from the logs some errors like these:
>
> Aug 21 15:24:53 domU-12-31-39-0C-1A-2B pengine: [3816]: ERROR:
> is_op_dup: Operation resMySQL-monitor-10-0 is a duplicate of
> resMySQL-monitor-10
> Aug 21 15:24:53 domU-12-31-39-0C-1A-2B pengine: [3816]: ERROR:
> is_op_dup: Do not use the same (name, interval) combination more than
> once per resource
> Aug 21 15:24:53 domU-12-31-39-0C-1A-2B pengine: [3816]: ERROR:
> is_op_dup: Operation resMySQL-monitor-10-0 is a duplicate of
> resMySQL-monitor-10
> Aug 21 15:24:53 domU-12-31-39-0C-1A-2B pengine: [3816]: ERROR:
> is_op_dup: Do not use the same (name, interval) combination more than
> once per resource
> Aug 21 15:24:53 domU-12-31-39-0C-1A-2B pengine: [3816]: ERROR:
> is_op_dup: Operation resMySQL-monitor-10-0 is a duplicate of
> resMySQL-monitor-10
> Aug 21 15:24:53 domU-12-31-39-0C-1A-2B pengine: [3816]: ERROR:
> is_op_dup: Do not use the same (name, interval) combination more than
> once per resource
> Aug 21 15:24:53 domU-12-31-39-0C-1A-2B pengine: [3816]: ERROR:
> is_op_dup: Operation resMySQL-monitor-10-0 is a duplicate of
> resMySQL-monitor-10
> Aug 21 15:24:53 domU-12-31-39-0C-1A-2B pengine: [3816]: ERROR:
> is_op_dup: Do not use the same (name, interval) combination more than
> once per resource
> Aug 21 15:24:53 domU-12-31-39-0C-1A-2B pengine: [3816]: ERROR:
> is_op_dup: Operation resMySQL-monitor-10-0 is a duplicate of
> resMySQL-monitor-10
> Aug 21 15:24:53 domU-12-31-39-0C-1A-2B pengine: [3816]: ERROR:
> is_op_dup: Do not use the same (name, interval) combination more than
> once per resource
> Aug 21 15:24:53 domU-12-31-39-0C-1A-2B pengine: [3816]: ERROR:
> is_op_dup: Operation resMySQL-monitor-10-0 is a duplicate of
> resMySQL-monitor-10
> Aug 21 15:24:53 domU-12-31-39-0C-1A-2B pengine: [3816]: ERROR:
> is_op_dup: Do not use the same (name, interval) combination more than
> once per resource
> Aug 21 15:24:53 domU-12-31-39-0C-1A-2B pengine: [3816]: ERROR:
> is_op_dup: Operation resMySQL-monitor-10-0 is a duplicate of
> resMySQL-monitor-10
> Aug 21 15:24:53 domU-12-31-39-0C-1A-2B pengine: [3816]: ERROR:
> is_op_dup: Do not use the same (name, interval) combination more than
> once per resource
>
> and in fact, even if I manually kill the process in a node, the cluster
> isn't aware and does not react.
>
> What is wrong with this ms resource?
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
|
