<div>
If your database is large enough that this is a problem it is usually better to run your dump off a slave rather than the master.
</div>
<div><br>-- <br>Richard Taylor<br><br></div>
<p style="color: #a0a0a0;">On Monday, 8 August 2011 at 11:57, Jay Caines-Gooby wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div>On 8 August 2011 11:53, Andrew Stewart <<a href="mailto:boss@airbladesoftware.com">boss@airbladesoftware.com</a>> wrote:<br><blockquote type="cite"><div>Tim,<br><br><blockquote type="cite"><div>I had a similar problem with CentOS. mysqldump was stalling everything for a couple of minutes when it ran.<br><br>Saw some pretty epic query times popping up in NewRelic RPM around that time. The site just stalled for a few minutes.<br><br>Pingdom reported a minute or two of downtime.<br></div></blockquote><br>Thanks for the information. I use mysqldump too -- with increasing reluctance because I've been seeing the<br>same behaviour as you. As a stopgap measure I wrapped it in a timeout[1] but I think the real solution is to<br>move to Postgres and whatever backup mechanism it has.<br></div></blockquote><br>You can also use the --single-transaction option to mysqldump which<br>prevents it from locking up your app.<br><br><br>-- <br>Jay Caines-Gooby<br><a href="http://jay.gooby.org">http://jay.gooby.org</a><br><a href="mailto:jay@gooby.org">jay@gooby.org</a><br>+44 (0)7956 182625<br>twitter, skype & aim: jaygooby<br>gtalk: <a href="mailto:jaygooby@gmail.com">jaygooby@gmail.com</a><br>_______________________________________________<br>Chat mailing list<br><a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br><a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br></div></div></span>
</blockquote>
<div>
<br>
</div>