Hi,

I don't know what caused it, nor whether it's reproducable, but on an AIX system,
I just found out that both of the 4.0.1 masters (typical master=slave_of_master loop
using same source tree configuration) have created 100.000+ files of the replication 
log.

I can only think they are replicating the RESET MASTER command to eachother which
I have issued once:

mysql> SHOW BINLOG EVENTS IN 'rep_log.100587';
+----------------+-----+------------+-----------+---------+----------------------------------------+
| Log_name       | Pos | Event_type | Server_id | Log_seq | Info                       
|            |
+----------------+-----+------------+-----------+---------+----------------------------------------+
| rep_log.100587 | 4   | Rotate     | 3406120   | 2       | rep_log.100588;pos=4; 
|forced by master |
| rep_log.100587 | 45  | Stop       | 3406121   | 3       |                            
|            |
+----------------+-----+------------+-----------+---------+----------------------------------------+
2 rows in set (8.33 sec)

mysql> SHOW BINLOG EVENTS IN 'rep_log.002';
+-------------+-----+------------+-----------+---------+--------------------------------------------+
| Log_name    | Pos | Event_type | Server_id | Log_seq | Info                          
|             |
+-------------+-----+------------+-----------+---------+--------------------------------------------+
| rep_log.002 | 4   | Start      | 3406121   | 1       | Server ver: 4.0.1-alpha-log, 
|Binlog ver: 2 |
| rep_log.002 | 79  | Rotate     | 3406120   | 3       | rep_log.003;pos=4; forced by 
|master        |
| rep_log.002 | 117 | Stop       | 3406121   | 4       |                               
|             |
+-------------+-----+------------+-----------+---------+--------------------------------------------+
3 rows in set (0.00 sec)

mysql> SHOW BINLOG EVENTS IN 'rep_log.001';
+-------------+-----+------------+-----------+---------+--------------------------------------------+
| Log_name    | Pos | Event_type | Server_id | Log_seq | Info                          
|             |
+-------------+-----+------------+-----------+---------+--------------------------------------------+
| rep_log.001 | 4   | Start      | 3406121   | 1       | Server ver: 4.0.1-alpha-log, 
|Binlog ver: 2 |
| rep_log.001 | 79  | Stop       | 3406121   | 2       |                               
|             |
+-------------+-----+------------+-----------+---------+--------------------------------------------+
2 rows in set (0.00 sec)

I'll have to clean this up a.s.a.p as it's eating away inodes. I'll tar the directory 
to keep for reference, just in case you guys need it.

I have no way to check whether it's reproducable.

Best regards,

Melvyn Sopacua
WebMaster IDG.nl
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
If it applies, where it applies - this email is a personal
contribution and does not reflect the views of my employer
IDG.nl.
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\


---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to