<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi AJ,<br>
<br>
Thanks for that. We aren't doing any custom stuff with the
database, so my guess is that we will be just fine going forward
with this.<br>
<br>
Thanks again for the response!<br>
<br>
Steven<br>
<br>
On 01/28/2015 02:37 PM, AJ McKee wrote:<br>
</div>
<blockquote
cite="mid:CAPkjrhFSAbB1SVAs8KHTrNmYDRy-2531YrNty8RVz38jy-uaEQ@mail.gmail.com"
type="cite">
<div dir="ltr">Hi Steven,
<div><br>
</div>
<div>I went through this process sometime ago, and like you
changed to mixed mode replication for the MySQL backend.ÃÂ </div>
<div><br>
</div>
<div>If your underlying tables follow the pdns vanilla install,
you should not encounter any problem, in fact you should see a
good improvement on the performance of MySQL replication. This
is assuming you have no other DB that is being replicated.</div>
<div><br>
</div>
<div>If you have customised your tables, or have a custom
application accessing the DB, then it would be worthy to do a
review of the query patterns (Enable query logging) to
evaluate if there are any pitfalls. In particular watch out
for queries that affect a large dataset within your
application, however MIXED mode should determine the correct
strategy to use.ÃÂ </div>
<div><br>
</div>
<div>An excellent write up on Statement, Row and Mixed modes is
here;ÃÂ <a moz-do-not-send="true"
href="http://mysql.wingtiplabs.com/documentation/row639ae/configure-row-based-or-mixed-mode-replication">http://mysql.wingtiplabs.com/documentation/row639ae/configure-row-based-or-mixed-mode-replication</a>
and explains it much better than I or the MySQL docs could.</div>
<div><br>
</div>
<div>In short, I can't see any disadvantage to MIXED mode, but
of course it depends on your setup.</div>
<div><br>
</div>
<div>Best of luck</div>
<div>AJ</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 28 January 2015 at 18:24, Steven
Spencer <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:steven.spencer@kdsi.com" target="_blank">steven.spencer@kdsi.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Greetings,<br>
<br>
We have been using PDNS with gmysql back end for a long time
and because of some legacy Xen server retirement projects,
We have decided to do a forklift upgrade of our PDNS install
at the same time. Currently, our primary and secondary DNS
servers are using 2.9.22 and we will be moving to 3.3.1-1.
I've read all of the upgrade notes with the mysql schema
changes, etc., and those items will be no issue to
accomplish. My concern is that we are doing database
replication using the old style replication methodology (not
the mysql cluster methodology) and I'm wondering what, if
anything, the change in the binlog_format from STATEMENT,
which is what it currently is, to MIXED will do to
replication.<br>
<br>
Our current set up is a mysql DNS master server that has the
web front-end on it and is set up as the master for the
database with both the primary and secondary DNS servers set
as slaves to this machine. We also have external
pdns-recursor machines that were recently updated to 3.6.2-1
and are working fine. Our implementation is on CentOS 5
(currently) and will be moving to CentOS 6.<br>
<br>
Thanks for any light that you might be able to shed on this
process.<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
-- <br>
Steven G. Spencer, Network Administrator<br>
<br>
<br>
_______________________________________________<br>
Pdns-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Pdns-users@mailman.powerdns.com"
target="_blank">Pdns-users@mailman.powerdns.com</a><br>
<a moz-do-not-send="true"
href="http://mailman.powerdns.com/mailman/listinfo/pdns-users"
target="_blank">http://mailman.powerdns.com/mailman/listinfo/pdns-users</a><br>
</font></span></blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">AJ McKee<br>
phone:ÃÂ +353 83 1130 545<br>
profile:ÃÂ <a moz-do-not-send="true"
href="http://linkedin.com/in/ajmkee" target="_blank">http://linkedin.com/in/ajmkee</a><br>
jid:ÃÂ ÃÂ ÃÂ ÃÂ <a moz-do-not-send="true"
href="mailto:aj.mckee@druid-dns.com" target="_blank">aj.mckee@druid-dns.com</a><br>
blog:ÃÂ ÃÂ <a moz-do-not-send="true"
href="http://aj.mc-kee.com/" target="_blank">http://aj.mc-kee.com/</a><br>
twitter: @ajmckee</div>
</div>
</blockquote>
<br>
</body>
</html>