<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
Ruzsinszky Attila wrote:
<blockquote
cite="mid:AANLkTin492kQJvRJfx=a2Y2+1D7YX3Z7U=4+2t9F=A9n@mail.gmail.com"
type="cite">
<pre wrap="">Hi,
</pre>
<blockquote type="cite">
<pre wrap="">And now (officially) RHCS can also use Pacemaker
<a class="moz-txt-link-freetext" href="http://theclusterguy.clusterlabs.org/post/1551292286">http://theclusterguy.clusterlabs.org/post/1551292286</a>
</pre>
</blockquote>
<pre wrap=""><!---->Nice.
</pre>
<blockquote type="cite">
<pre wrap="">Yeah, like I said, Master-Master and Pacemaker without a proper resource
agent will cause issues.
</pre>
</blockquote>
<pre wrap=""><!---->Yes.
</pre>
<blockquote type="cite">
<pre wrap="">big problems. Now let me explain this, a 2-node Multi-Master MySQL setup
means setting up every node as both Master and Slave, node 1's Master
replicates asynchronously to node 2's Slave and node 2's Master replicates
asynchronously to node 1's Slave. The replication channels between the two
are not redundant, nor do they recover from failure automatically and you
have to manually set the auto-increment-increment and auto-increment-offset
so that you don't have primary key collisions.
</pre>
</blockquote>
<pre wrap=""><!---->Clear.
</pre>
<blockquote type="cite">
<pre wrap="">each server. Looking at how DRBD handles these kinds of things is one way to
go about it, but ... it's a huge task and there are a lot of things that can
go terribly wrong.
</pre>
</blockquote>
<pre wrap=""><!---->:-(
</pre>
<blockquote type="cite">
<pre wrap="">So again, for the third time, the problem is not the Multi-Master setup, nor
it is Pacemaker, it's just a very specific use case for which a resource
agent wasn't written.
</pre>
</blockquote>
<pre wrap=""><!---->OK.
So now almost the only one possibilities is DRBD+MySQL?
</pre>
</blockquote>
Afaik, yes, I'm hoping someone will step in and say otherwise, but to
the best of my knowledge, the only implementation between MySQL and
Pacemaker is represented by the mysql and mysql-proxy resource agents
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<a href="http://www.linux-ha.org/wiki/Resource_Agents">http://www.linux-ha.org/wiki/Resource_Agents</a><br>
<br>
The mysql RA controls a single MySQL instance and the rest of the HA
setup is done via DRBD Master-Slave resources.<br>
<br>
Regards,<br>
<br>
Dan<br>
<blockquote
cite="mid:AANLkTin492kQJvRJfx=a2Y2+1D7YX3Z7U=4+2t9F=A9n@mail.gmail.com"
type="cite">
<pre wrap="">
TIA,
Ruzsi
_______________________________________________
Pacemaker mailing list: <a class="moz-txt-link-abbreviated" href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a>
<a class="moz-txt-link-freetext" href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a>
Project Home: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org">http://www.clusterlabs.org</a>
Getting started: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs: <a class="moz-txt-link-freetext" href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Dan FRINCU
Systems Engineer
CCNA, RHCE
Streamwide Romania
</pre>
</body>
</html>