Flusing MySQL replication logs

MySQL master servers won’t remove their logs automatically when slaves are done with them. You can set expire_logs_days to remove them after a certain number of days. But, you are not assured that a slave is done with the logs. So, we wrote a script to connect to slaves and then purge logs on the master servers. It works for us. Your mileage may vary. BSD style license. Enjoy.

flush_mysql_master.php.gz

This entry was posted on Thursday, February 28th, 2008 at 10:07 pm and is filed under MySQL, PHP. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

6 Responses to “Flusing MySQL replication logs”

  1. Links for 2008-02-28 [del.icio.us] : e-Spot.se Says:
    February 29, 2008 at 9:00 am

    [...] Flusing MySQL replication logs « Ramblings of a web guy [...]

  2. otis Says:
    February 29, 2008 at 11:38 am

    The zip file seems to be corrupted

  3. Foobar Says:
    February 29, 2008 at 1:07 pm

    It is not a ZIP. It is Gzipped as the extension gz states and it extracts just fine.

  4. anonymous Says:
    February 29, 2008 at 9:58 pm

    The file is indeed corrupted, even after I tried with gzip -d filename. Can you please post it again?!

  5. doughboy Says:
    February 29, 2008 at 10:41 pm

    Apparently my proxies are acting up. I need to figure out why they are compressing non text content.

    I updated the link in the post to this working link:
    http://content.dealnews.com/dealnews/developers/flush_mysql_master.php.gz

  6. Propiedad Privada » Blog Archive » Ensalada de enlaces de Bases de Datos Says:
    March 3, 2008 at 3:56 pm

    [...] Flusing MySQL replication logs [...]

Comments are closed.