<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<!-- Template generated by Exclaimer Mail Disclaimers on 10:46:07 Montag, 30 Januar 2012 -->
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css">P.abd03441-7d3a-47dc-ab5f-8a54a3cc2c8d {
MARGIN: 0cm 0cm 0pt
}
LI.abd03441-7d3a-47dc-ab5f-8a54a3cc2c8d {
MARGIN: 0cm 0cm 0pt
}
DIV.abd03441-7d3a-47dc-ab5f-8a54a3cc2c8d {
MARGIN: 0cm 0cm 0pt
}
TABLE.abd03441-7d3a-47dc-ab5f-8a54a3cc2c8dTable {
MARGIN: 0cm 0cm 0pt
}
DIV.Section1 {
page: Section1
}
</style>
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.E-MailFormatvorlage17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:824205128;
mso-list-type:hybrid;
mso-list-template-ids:-108339690 1312598986 67567619 67567621 67567617 67567619 67567621 67567617 67567619 67567621;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="DE" link="blue" vlink="purple">
<p class="abd03441-7d3a-47dc-ab5f-8a54a3cc2c8d"></p>
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Hi!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I’m on the lookout for alternatives to our current MySQL “cluster”, which is an Active/Standby solution with MySQL on DRBD.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">With increasing customer demand for a faster failover, we want an Active/Passive or even an Active/Active cluster.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Currently we run a Tomcat application, which works in Active/Passive-Mode. The applications on the active node communicate it’s status via a MySQL database to the passive node. In our current setup, both nodes run the
tomcat application but only one holds the database (due to the setup with DRBD). For faster failovers, we’d rather want the database to be active on both nodes. It’s not necessary, that it can written on both nodes, but read access would be desirable. The
thought is, that switching the “master status” of a database might be quicker than switching DRBD’s master status, unmounting and mounting the file system and stopping and starting the database.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">A MySQL/Pacemaker cluster with replication as described in
<a href="http://www.mysqlperformanceblog.com/2011/11/29/percona-replication-manager-a-solution-for-mysql-high-availability-with-replication-using-pacemaker/">
http://www.mysqlperformanceblog.com/2011/11/29/percona-replication-manager-a-solution-for-mysql-high-availability-with-replication-using-pacemaker/</a> thus looked very promising, but it seems to be not yet mature enough for a production environment. Please
do correct men if I’m wrong there, I’m really interested in your experience with this solution in a real world scenario.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Are there perhaps other howtos describing Pacemaker and MySQL replication?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The second idea was using the native MySQL NDB clustering with Pacemaker.
<a href="http://www.mysqlperformanceblog.com/2010/05/19/pacemaker-please-meet-ndb-cluster-or-using-pacemakerheartbeat-to-start-a-ndb-cluster/">
http://www.mysqlperformanceblog.com/2010/05/19/pacemaker-please-meet-ndb-cluster-or-using-pacemakerheartbeat-to-start-a-ndb-cluster/</a> (from 2010, uses heartbeat and pacemaker) and
<a href="http://www.howtoforge.com/loadbalanced_mysql_cluster_debian">http://www.howtoforge.com/loadbalanced_mysql_cluster_debian</a> (from 2008, uses pure heartbeat). Are there any more recent “howtos” on pacemaker and MySQL NDB 7.x describe this. Can you
provide me with your opinions and field reports on these setups?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Looking forward to your upcoming mails,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Andreas<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<p></p>
<p class="abd03441-7d3a-47dc-ab5f-8a54a3cc2c8d"> </p>
<p class="abd03441-7d3a-47dc-ab5f-8a54a3cc2c8d">----------------------------<br>
CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef.<br>
Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 9136)<br>
Geschäftsführer/Managing Director: Anke Höfer </p>
<p class="abd03441-7d3a-47dc-ab5f-8a54a3cc2c8d"> ----------------------------</p>
<p class="abd03441-7d3a-47dc-ab5f-8a54a3cc2c8d"> </p>
<p class="abd03441-7d3a-47dc-ab5f-8a54a3cc2c8d"></p>
</body>
</html>