[Pacemaker] Master/Slave Resource and Stop/Start of HA System

Eliot Gable egable at broadvox.com
Mon Jul 27 16:37:11 UTC 2009


Bug 2162 has been opened for this:

http://developerbugs.linux-foundation.org/show_bug.cgi?id=2162

Let me know if you need any additional information. I assume you should be able to reproduce it on your own with any master/slave resource. If not, then we can look at what's different with my setup from your test setup.



-----Original Message-----
From: Andrew Beekhof [mailto:andrew at beekhof.net]
Sent: Monday, July 27, 2009 2:39 AM
To: pacemaker at oss.clusterlabs.org
Subject: Re: [Pacemaker] Master/Slave Resource and Stop/Start of HA System

http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

2009/7/26 Димитър Бойн <dboyn at postpath.com>:
> I observe the same. Definitely a bug.
>
> How do I file (follow) a bug?
>
>
>
> From: Andrew Beekhof
> Sent: Friday, July 24, 2009 5:00 AM
> To: pacemaker at clusterlabs.org
> Subject: Re: [Pacemaker] Master/Slave Resource and Stop/Start of HA System
>
>
>
> I'd guess the master preference (in the status section) got lost somehow.
>
> You should probably file a bug.
>
>
>
> On Jul 23, 2009, at 11:24 PM, Eliot Gable wrote:
>
> Ok, it does not actually stop the master, but it DOES demote the master to
> slave.
>
>
>
>
>
> From: Eliot Gable [mailto:egable at broadvox.com]
> Sent: Thursday, July 23, 2009 5:23 PM
> To: pacemaker at 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 at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
>
>
> -- Andrew
>
>
>
>
>
>
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
>

_______________________________________________
Pacemaker mailing list
Pacemaker at oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

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.




More information about the Pacemaker mailing list