Ok, it does not actually stop the master, but it DOES demote the master to slave.
From: Eliot Gable [mailto:ega...@broadvox.com] Sent: Thursday, July 23, 2009 5:23 PM To: pacemaker@oss.clusterlabs.org Subject: [Pacemaker] Master/Slave Resource and Stop/Start of HA System Running Pacemaker 1.0.4. With my Master/Slave resource in Master on node1 and Slave on node2, if I /etc/init.d/heartbeat stop on node2, I see the slave go down and node1 stays master in crm_mon. When it finishes, node2 is in OFFLINE status (no unclean modifier). When I then /etc/init.d/heartbeat start on node2, the MASTER on node1 STOPS and then both node1 and node2 come up in SLAVE and then node1 is promoted to MASTER. Is this supposed to happen? I would have expected the master to stay in master state and node2 to just start in slave and stay that way. I need to be able to restart the slave without impacting the master. If the master goes down or even goes into slave mode, everything is dead. No traffic passes. It is the same as an outage. So, is it my config, or is this normal behavior? ________________________________ CONFIDENTIAL. This e-mail and any attached files are confidential and should be destroyed and/or returned if you are not the intended and proper recipient. ________________________________ CONFIDENTIAL. This e-mail and any attached files are confidential and should be destroyed and/or returned if you are not the intended and proper recipient.
_______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
