mysqld .bin files

Forum Moderators: open

Message Too Old, No Replies

mysqld .bin files

glimbeek

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

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?

Demaestro

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

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

mack

4:34 pm on Feb 19, 2010 (gmt 0)

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.

Demaestro

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

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.

mysqld .bin files

glimbeek

Demaestro

mack

Demaestro

Join The Conversation

Moderators and Top Contributors

Hot Threads This Week