EmergencyEMERGENCY? Get 24/7 Help Now!

Win a free ticket to RailsConf!

 | May 15, 2011 |  Posted In: MySQL

PREVIOUS POST
NEXT POST

I have one free ticket to give away to RailsConf next week in Baltimore! Post a comment to win, and if you aren’t the winner, I’ll give you a discount code for Percona Live as a consolation prize.

Here’s the catch: you have to find at least one thing wrong with the following typical logrotate configuration for MySQL. This should be easy even if you’re not a MySQL expert :-)

PREVIOUS POST
NEXT POST
Baron Schwartz

Baron is the lead author of High Performance MySQL. He is a former Percona employee.

10 Comments

  • Everything. Finding things wrong with it is like shooting fish in a barrel. I’ll blog about it someday.

  • Hmm. If I remember logrotate correctly, the compress gets executed before the flush-logs; so you run the risk of adding lines to an already-compressed logfile – and maybe lines added *during* compression will be lost depending on the compression utility’s behaviour.

  • Vitaly, I either confused you, or you are extremely clever and funny :)

    I’ll write a blog post sometime about what’s wrong with the default logrotate scripts for MySQL. The free ticket goes to John!

  • * It’s a bit harder to ‘rotate’ mysql databases then a text files;
    * InnoDB row will not exceed 8000 bytes under some conditions;
    * MySQL is an additional point of failure;

    Is it enough? :-)

  • For bonus points (but no bonus tickets), tell me what’s busted about logging to syslog with MySQL, too!

  • You don’t want the “create 600 mysql mysql” line — it’s commented out in the default config.

    But the real problem is you’re logging to a file and not syslog :)

Leave a Reply