Hello.<div>Check it out <a href="https://code.launchpad.net/percona-prm">https://code.launchpad.net/percona-prm</a>. </div><div>And presentation: <a href="http://www.percona.com/files/presentations/percona-live/nyc-2011/PerconaLiveNYC2011-MySQL-High-Availability-with-Pacemaker.pdf">http://www.percona.com/files/presentations/percona-live/nyc-2011/PerconaLiveNYC2011-MySQL-High-Availability-with-Pacemaker.pdf</a><br>
<div><br><div class="gmail_quote">2011/8/15 Michael Szilagyi <span dir="ltr"><<a href="mailto:mszilagyi@gmail.com">mszilagyi@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I'm already using the mysql RA file from <a href="https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/mysql" target="_blank">https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/mysql</a> (which also seems to have replication support in it).<div>
<br></div><div>Basically what seems to be happening is that pacemaker detects that the master has dropped and promotes a slave up to master. However, it is not properly reconfiguring the slaves with a CHANGE MASTER TO. I can see some lines in the ocf file that relate to changing master but it isn't setting it up properly. If I login to the slave and issue a CHANGE MASTER TO ... / START SLAVE then replication will start up normally again.</div>
<div><br></div><div>Since I can see that the script does allow the master host to get set when going through set/unset_master I'm hoping it's just something I'm missing and not a limitation of using Pacemaker to manage the sql replication cluster.<br>
<br></div><div>Hopefully someone can point me at what I am missing.</div><div><br></div><div>-Mike.</div><div><div></div><div class="h5"><div><br><div class="gmail_quote">On Mon, Aug 15, 2011 at 1:56 AM, Dan Frincu <span dir="ltr"><<a href="mailto:df.cluster@gmail.com" target="_blank">df.cluster@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<div><br>
On Sat, Aug 13, 2011 at 2:53 AM, Michael Szilagyi <<a href="mailto:mszilagyi@gmail.com" target="_blank">mszilagyi@gmail.com</a>> wrote:<br>
> I'm new to Pacemaker and trying to understand exactly what it can and can't<br>
> do.<br>
> I currently have a small, mysql master/slave cluster setup that is getting<br>
> monitored within Heartbeat/Pacemaker: What I'd like to be able to do (and<br>
> am hoping Pacemaker will do) is to have 1 node designated as Master and in<br>
> the event of a failure, automatically promote a slave to master and realign<br>
> all of the existing slaves to be slaves of the newly promoted master.<br>
> Currently what seems to be happening, however, is heartbeat correctly sees<br>
> that a node goes down and pacemaker promotes it up to master but the<br>
> replication is not adjusted so that it is now feeding everyone else. It<br>
> seems like this should be possible to do from within Pacemaker but I feel<br>
> like I'm missing a part of the puzzle. Any suggestions would be<br>
> appreciated.<br>
<br>
</div>You could try the mysql RA => from<br>
<a href="https://github.com/fghaas/resource-agents/blob/master/heartbeat/mysql" target="_blank">https://github.com/fghaas/resource-agents/blob/master/heartbeat/mysql</a><br>
Last I heard, it had replication support.<br>
<br>
HTH.<br>
<div><div></div><div><br>
><br>
> Here's an output of my crm configure show:<br>
> node $id="7deca2cd-9a64-476c-8ea2-372bca859a4f" four \<br>
> attributes 172.17.0.130-log-file-p_sql="mysql-bin.000013"<br>
> 172.17.0.130-log-pos-p_sql="632"<br>
> node $id="9b355ab7-8c81-485c-8dcd-1facedde5d03" three \<br>
> attributes 172.17.0.131-log-file-p_sql="mysql-bin.000020"<br>
> 172.17.0.131-log-pos-p_sql="106"<br>
> primitive p_sql ocf:heartbeat:mysql \<br>
> params config="/etc/mysql/my.cnf" binary="/usr/bin/mysqld_safe"<br>
> datadir="/var/lib/mysql" \<br>
> params pid="/var/lib/mysql/novaSQL.pid" socket="/var/run/mysqld/mysqld.sock"<br>
> \<br>
> params max_slave_lag="120" \<br>
> params replication_user="novaSlave" replication_passwd="nova" \<br>
> params additional_parameters="--skip-external-locking<br>
> --relay-log=novaSQL-relay-bin --relay-log-index=relay-bin.index<br>
> --relay-log-info-file=<a href="http://relay-bin.info" target="_blank">relay-bin.info</a>" \<br>
> op start interval="0" timeout="120" \<br>
> op stop interval="0" timeout="120" \<br>
> op promote interval="0" timeout="120" \<br>
> op demote interval="0" timeout="120" \<br>
> op monitor interval="10" role="Master" timeout="30" \<br>
> op monitor interval="30" role="Slave" timeout="30"<br>
> primitive p_sqlIP ocf:heartbeat:IPaddr2 \<br>
> params ip="172.17.0.96" \<br>
> op monitor interval="10s"<br>
> ms ms_sql p_sql \<br>
> meta target-role="Started" is-managed="true"<br>
> location l_sqlMaster p_sqlIP 10: three<br>
> location l_sqlSlave1 p_sqlIP 5: four<br>
> property $id="cib-bootstrap-options" \<br>
> dc-version="1.0.9-unknown" \<br>
> cluster-infrastructure="Heartbeat" \<br>
> stonith-enabled="false" \<br>
> no-quorum-policy="ignore" \<br>
> last-lrm-refresh="1313187103"<br>
><br>
> Thanks!<br>
> -Mike.<br>
</div></div>> _______________________________________________<br>
> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">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:<br>
> <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>
><br>
<br>
<br>
<br>
--<br>
Dan Frincu<br>
CCNA, RHCE<br>
<br>
_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">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>
</blockquote></div><br></div>
</div></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><br clear="all"><div><br></div>-- <br>Viacheslav Biriukov<br>BR<br><div><a href="http://biriukov.com" target="_blank">http://biriukov.com</a></div><br>
</div></div>