MySQL Forums
Forum List  »  Replication

Disappearing Binlogs
Posted by: Solomon Chang
Date: April 08, 2009 12:55PM

I'm using MySQL 5.1.31 on CentOS 5, which is exhibiting odd behavior when it comes to replication.

My Binary Log keep disappearing. I wasn't sure when this was happening, but I just happened to capture this while I working:

[root@masdev01 mysql]# cd /var/log/mysql
[root@masdev01 mysql]# ls -l
total 3028
-rw-rw---- 1 mysql root 13598 Mar 5 15:25 error.log
-rw-rw---- 1 mysql mysql 292 Mar 4 18:34 masdev01.000002
-rw-rw---- 1 mysql mysql 292 Mar 4 18:34 masdev01.000003
-rw-rw---- 1 mysql mysql 167 Mar 5 15:25 masdev01.000004
-rw-rw---- 1 mysql mysql 125 Mar 5 15:25 masdev01.000006
-rw-rw---- 1 mysql mysql 601305 Mar 9 12:36 masdev01.000012
-rw-rw---- 1 mysql mysql 648719 Mar 10 18:49 masdev01.000085
-rw-rw---- 1 mysql mysql 1723289 Apr 8 11:45 masdev01.000092
-rw-rw---- 1 mysql mysql 292 Apr 8 10:54 masdev01.000107
-rw-rw---- 1 mysql mysql 250 Apr 8 10:54 masdev01.000108
-rw-rw---- 1 mysql mysql 31 Apr 7 19:31 masdev01.index
-rw-rw---- 1 mysql mysql 496 Apr 7 19:33 mysqld.log
-rw-rw---- 1 mysql mysql 6014 Apr 7 19:28 mysqld.log-old
[root@masdev01 mysql]# cat masdev01.index
/var/log/mysql/masdev01.000092
[root@masdev01 mysql]# mysql -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 113362
Server version: 5.1.31-log MySQL Community Server (GPL) by Remi

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> flush master;
Query OK, 0 rows affected (0.01 sec)

mysql> exit
Bye
[root@masdev01 mysql]# ls -l
total 1344
-rw-rw---- 1 mysql root 13598 Mar 5 15:25 error.log
-rw-rw---- 1 mysql mysql 292 Mar 4 18:34 masdev01.000002
-rw-rw---- 1 mysql mysql 292 Mar 4 18:34 masdev01.000003
-rw-rw---- 1 mysql mysql 167 Mar 5 15:25 masdev01.000004
-rw-rw---- 1 mysql mysql 125 Mar 5 15:25 masdev01.000006
-rw-rw---- 1 mysql mysql 601305 Mar 9 12:36 masdev01.000012
-rw-rw---- 1 mysql mysql 648719 Mar 10 18:49 masdev01.000085
-rw-rw---- 1 mysql mysql 292 Apr 8 10:54 masdev01.000107
-rw-rw---- 1 mysql mysql 250 Apr 8 10:54 masdev01.000108
-rw-rw---- 1 mysql mysql 106 Apr 8 11:49 masdev01.000109
-rw-rw---- 1 mysql mysql 31 Apr 8 11:49 masdev01.index
-rw-rw---- 1 mysql mysql 496 Apr 7 19:33 mysqld.log
-rw-rw---- 1 mysql mysql 6014 Apr 7 19:28 mysqld.log-old
[root@masdev01 mysql]#

In a nutshell, I go to the MySQL prompt and flush master, which should close out the current binlog and start a new one. It does, but in the process, masdev01.000092 has completely disappeared! It was a rather binlog too!
You can probably tell from all those skips in the binlog numbering that this is not an isolated occurrence, and seems to happen with alarming regularity. What's going on with MySQL? Is this release just buggy? Do I need to downgrade to another version?


Solomon

Options: ReplyQuote


Subject
Views
Written By
Posted
Disappearing Binlogs
3552
April 08, 2009 12:55PM
2070
April 08, 2009 02:16PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.