June 19, 2013

Post: Rotating MySQL slow logs safely

…. Disable MySQL slow logs during rotation Flushing logs takes time. Meanwhile, queries are still being executed. To prevent MySQL from filling the slow log buffer, we disable the MySQL slow logs temporarily during log rotation. Putting it all together Here is a logrotate configuration file for a slow log

Post: Is your MySQL buffer pool warm? Make it sweat!

slow.log`, except that it knows how to follow the log stream across log rotation events. On the standby server, the logs are replayed with Percona Playback by streaming the slow log

Comment: Rotating MySQL slow logs safely

“To prevent MySQL from filling the slow log buffer, we disable the MySQL slow logs temporarily during log rotation.” Wouldn’t that be in the prerotate section? I don’t see one in the stanza provided.

Post: A (prototype) lower impact slow query log

…examine how we could provide slow query log type functionality to our users. The slow query log code inside the MySQL server does several … the buffer) for concurrency – pushing all the concurrency problems down into the operating system. The main challenge with this strategy is log file rotation

Comment: Percona RPMS for RedHat 5 / CentOS 5 x86_64

… for sharing. Rumor has it you use the Information Schema to export the output from the monitoring rather than SHOW {TABLE,USER,INDEX}_STATISTICS. That sounds great. We are still in a MySQL 4.0 mindset and don’t know much about the Information Schema. We just added support to rotate the slow query log. And…

Comment: A (prototype) lower impact slow query log

… why someone would make a extended_slow_query_log.log.1 -> (somewhere/lese to change the folder of the rotated query log file (they couldn’t move… file rotation would be taking place at all). However, the log folder needs to be only writable by mysql to prevent the TOCTTOU, so only the

Post: Be careful rotating MySQL logs

If you enable logging of all queries as “slow queries” using the patch or MySQL 5.1 you can get log file to grow huge. Same may happen with general log file… delete the log file you no more need. It can be also good idea to hook up log rotate to take care of MySQL logs so…

Post: Automation: A case for synchronous replication

rotation for some reason… with essentially zero impact to the end user. The performance problems are also handled different way – theMySQL Replication is handled by cluster internally – for example if timeouts are reconfigured the transient network slowness

Comment: How to calculate a good InnoDB log file size

… to the system and see how often the log rotates — for instance, just now here’s a sample from a production machine: /var/lib/mysqlslow time, but as you can see, there’s at *least* about 2 hours’ worth of space in the logs, as the logfile was “rotated… if the peak time lasts 1 hour and the log rotates approximately every 2 hours, I probably don’t want to cut the log file size…