Welcome to WebmasterWorld Guest from 54.145.174.178

Forum Moderators: open

Message Too Old, No Replies

mysqld .bin files

   
1:21 pm on Feb 19, 2010 (gmt 0)

5+ Year Member



The .bin files on my server are getting to large and they crash my mysql server at times.

This is obviously not something I want happening.

Now I can create a cronjob that removes the bin files at set intervals OR I can disable bin "logging" all together.

Before I do either of those two, I was wondering what use is a .bin file and what effect will the above two option have?

Can I remove .bin files whenever I feel like it? What do I miss/what happens if I disable .bin logging completely?
3:21 pm on Feb 19, 2010 (gmt 0)

WebmasterWorld Senior Member demaestro is a WebmasterWorld Top Contributor of All Time 10+ Year Member



Well I can't speak to the consequences of not having the bin logging but you can delete them without losing data.

If you issue these commands at certain intervals you can get rid of them, or as you mentioned you can turn of bin logging.

mysql> flush logs;

mysql> reset master;

You can view the contents of the bin files by using mysqlbinlog and piping the output to a txt file

sudo mysqlbinlog /var/lib/mysql/mysqld-bin.000001 > log.txt
4:34 pm on Feb 19, 2010 (gmt 0)

WebmasterWorld Administrator mack is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month



are .bin files not in some way related to replication? I have had issues in the past with very large bin files and removed them with no issue.

Mack.
6:07 pm on Feb 19, 2010 (gmt 0)

WebmasterWorld Senior Member demaestro is a WebmasterWorld Top Contributor of All Time 10+ Year Member



I am going by memory here but I think that the bin files also have a log of transactions but I may be wrong on that.
 

Featured Threads

Hot Threads This Week

Hot Threads This Month