[Pacemaker] Monitor and standby

[Lars Marowsky-Bree]

On 2013-07-03T12:21:37, Denis Witt <denis.witt at concepts-and-training.de> wrote:

> Hi List,
> 
> we have a two node cluster (test1-node1, test1-node2) with an additional
> quorum node (test1). On all nodes MySQL is running. test1-node1 and
> test1-node2 sharing the MySQL-Database via DRBD, so only one Node
> should run MySQL. On test1 there is a MySQL-Slave connected to
> test1-node1/test1-node2. test1 is always in Standby-Mode.
> 
> The problem is now that the MySQL-Slave on test1 is shut down by crmd:
> 
> Jul  3 12:05:12 test2 crmd: [5945]: info: te_rsc_command: Initiating action 22: monitor p_mysql_monitor_0 on test2 (local)
> Jul  3 12:05:14 test2 pengine: [5944]: ERROR: native_create_actions: Resource p_mysql (lsb::mysql) is active on 2 nodes attempting recovery
> Jul  3 12:05:14 test2 pengine: [5944]: notice: LogActions: Restart p_mysql#011(Started test2-node1)
> Jul  3 12:05:15 test2 crmd: [5945]: info: te_rsc_command: Initiating action 54: stop p_mysql_stop_0 on test2 (local)
> 
> From my understanding this shouldn't happen as test1 was set to standby
> before:
> 
> Jul  3 12:04:48 test2 cib: [5940]: info: cib:diff: +           <nvpair id="nodes-test2-standby" name="standby" value="on" />
> 
> How could we solve this?

"monitor_0" is the initial probe; that happens when a node newly starts,
or after a resource cleanup. The cluster tries to discover where
resources are, and that includes standby nodes. It'll stop them where
they don't belong.

Solve it by not having the resource active on the standby node.

If the lsb init script isn't powerful enough to differentiate between
different instances, use the OCF resource agent for mysql.


Regards,
    Lars

-- 
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde