Dan thanks for you reply and the documentation. That all makes sense. I guess what I am confused about how to tell pacemaker to start mysql on both servers. My limited experience so far has been that pacemaker starts up mysql on the primary and in the event of a failure it will move the virtual ip to secondary node and start up the mysql service. The problem is that mysql is running in master/slave mode for replication and therefore needs to be running all the time on the secondary. Do I need a clone resource for this? Thanks again.<div>
<br></div><div>F.<br><br><div class="gmail_quote">On Fri, Jul 23, 2010 at 3:33 AM, Dan Frincu <span dir="ltr"><<a href="mailto:dfrincu@streamwide.ro">dfrincu@streamwide.ro</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff" text="#000000">
First take a look at this
<a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a> <br>
It contains all you need for this kind of setup. I'm not aware if the
M/S relationship extends to other resources than DRBD, but in this case
you don't actually need a M/S relationship (from my point of view).<br>
<br>
1. Read in the document above about 'symmetric-cluster'<br>
2. Based on results from point 1, set the resources as being allowed
either to run anywhere or not, and add location constraints for each
primitive.<br>
3. Define mandatory ordering constraints for the mysql primitive, with
a higher priority on the node you wish to use as a Primary node and a
lower priority on the Secondary node (if Primary node fails, the
resource will failover to Secondary node)<br>
4. Define colocation so that VIP will always run where the mysql
resource runs.<br>
5. (optional) define mail alerts when resource failure occurs, define
what the mysql resource should do when the Primary node recovers,
should it remain on the Secondary node and be manually moved, should it
go back to the Primary node by itself, these are things you might want
to consider, but are not mandatory to the question asked, therefore the
"optional" at the beginning)<br>
<br>
Regards,<br>
Dan<br>
<br>
Freddie Sessler wrote:
<blockquote type="cite"><div><div></div><div class="h5">I have a quick question is the Master Slave setting in
pacemaker only allowed in regards to a DRBD device? Can you use it to
create other Master Slave relationships? Does all resource agents
potentially involved in this need to be aware of the Master Slave
relationship? I am trying to set up a pair fo mysql servers One is
replicating from the other(handled within mysql's my.cnf.) I basically
want to fail over the VIP of the primary node to the secondary
node(which also happens to be the mysql slave) in the event that the
primary has its mysql server stopped. I am not using DRBD at all. My
config looks like the following.
<div><br>
</div>
<div>
<div>node $id="0cd2bb09-00b6-4ce4-bdd1-629767ae0739" sipl-mysql-109</div>
<div>node $id="119fc082-7046-4b8d-a9a3-7e777b9ddf60" sipl-mysql-209</div>
<div>primitive p_clusterip ocf:heartbeat:IPaddr2 \</div>
<div><span style="white-space:pre-wrap"> </span>params
ip="10.200.131.9" cidr_netmask="32" \</div>
<div><span style="white-space:pre-wrap"> </span>op
monitor interval="30s"</div>
<div>primitive p_mysql ocf:heartbeat:mysql \</div>
<div><span style="white-space:pre-wrap"> </span>op
start interval="0" timeout="120" \</div>
<div><span style="white-space:pre-wrap"> </span>op
stop interval="0" timeout="120" \</div>
<div><span style="white-space:pre-wrap"> </span>op
monitor interval="10" timeout="120" depth="0"</div>
<div>ms ms_mysql p_mysql \</div>
<div><span style="white-space:pre-wrap"> </span>meta
master-max="1" master-node-max="1" clone-max="2" clone-node-max="1"</div>
<div>location l_master ms_mysql \</div>
<div><span style="white-space:pre-wrap"> </span>rule
$id="l_master-rule" $role="Master" 100: #uname eq sipl-mysql-109</div>
<div>colocation mysql_master_on_ip inf: p_clusterip ms_mysql:Master</div>
<div>property $id="cib-bootstrap-options" \</div>
<div><span style="white-space:pre-wrap"> </span>stonith-enabled="false"
\</div>
<div><span style="white-space:pre-wrap"> </span>no-quorum-policy="ignore"
\</div>
<div><span style="white-space:pre-wrap"> </span>start-failure-is-fatal="false"
\</div>
<div><span style="white-space:pre-wrap"> </span>expected-quorum-votes="2"
\</div>
<div><span style="white-space:pre-wrap"> </span>symmetric-cluster="false"
\</div>
<div><span style="white-space:pre-wrap"> </span>dc-version="1.0.9-89bd754939df5150de7cd76835f98fe90851b677"
\</div>
<div><span style="white-space:pre-wrap"> </span>cluster-infrastructure="Heartbeat"</div>
<div>rsc_defaults $id="rsc-options" \</div>
<div><span style="white-space:pre-wrap"> </span>resource-stickiness="100"</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div>What's happening is that mysql is never brought up due to the
following errors:</div>
<div><br>
</div>
<div>
<div>ul 22 16:15:07 sipl-mysql-109 pengine: [22890]: info:
native_color: Resource p_mysql:0 cannot run anywhere</div>
<div>Jul 22 16:15:07 sipl-mysql-109 pengine: [22890]: info:
native_color: Resource p_mysql:1 cannot run anywhere</div>
<div>Jul 22 16:15:07 sipl-mysql-109 pengine: [22890]: info:
native_merge_weights: ms_mysql: Rolling back scores from p_clusterip</div>
<div>Jul 22 16:15:07 sipl-mysql-109 pengine: [22890]: info:
master_color: ms_mysql: Promoted 0 instances of a possible 1 to master</div>
<div>Jul 22 16:15:07 sipl-mysql-109 pengine: [22890]: info:
native_color: Resource p_clusterip cannot run anywhere</div>
<div>Jul 22 16:15:07 sipl-mysql-109 pengine: [22890]: info:
master_color: ms_mysql: Promoted 0 instances of a possible 1 to master</div>
<div>Jul 22 16:15:07 sipl-mysql-109 pengine: [22890]: notice:
LogActions: Leave resource p_clusterip<span style="white-space:pre-wrap"> </span>(Stopped)</div>
<div>Jul 22 16:15:07 sipl-mysql-109 pengine: [22890]: notice:
LogActions: Leave resource p_mysql:0<span style="white-space:pre-wrap"> </span>(Stopped)</div>
<div>Jul 22 16:15:07 sipl-mysql-109 pengine: [22890]: notice:
LogActions: Leave resource p_mysql:1<span style="white-space:pre-wrap"> </span>(Stopped)</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div>I thought I may have overcome this with my location and
colocation directive but it failed. Could someone give me some feedback
on what I am trying to do, my config and the resulting errors?</div>
<div><br>
</div>
<div>Thanks</div>
<div>F.</div>
</div></div><pre><hr size="4" width="90%">
_______________________________________________
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs: <a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker" target="_blank">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a>
</pre>
</blockquote>
<br>
<pre cols="72">--
Dan FRINCU
Systems Engineer
CCNA, RHCE
Streamwide Romania
</pre>
</div>
<br>_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker" target="_blank">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a><br>
<br></blockquote></div><br></div>