I performed a LOAD DATA INFILE on two very large (2G and 997M) files to a db server that acts as a master to several slaves. The LOAD DATA was to a non-replicated db, and should not have been replicated, but it appears that, as it was not done as a LOAD DATA LOCAL INFILE, the data files were replicated (albeit uselessly) to the slave servers. Right off the bat, this resulted in a packet size issue which we resolved by adjusting max_allowed_packet, but the disk capacity of the file systems on the slave hosts filled to capacity. At this point, we were unable to set SQL_SLAVE_SKIP_COUNTER anywhere past the point of the data load and ended up stuck with broken replication on the slave machines. Here's a tail of an error log of one of the slaves: 031111 7:04:10 Error in Log_event::read_log_event(): 'read error', data_len: 825362754, event_type: 49 031111 7:04:10 Error reading relay log event: slave SQL thread aborted because of I/O error 031111 7:04:10 Slave: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: 0 031111 7:04:10 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'central-bin.041' position 649082785 As stated above, we cannot set SQL_SLAVE_SKIP_COUNTER to go beyond position 649082785. The master is Redhat Linux 9 running MySQL 4.0.15-standard-log, and the slaves are Redhat Linux 7.1 running MySQL 4.0.15-standard-log as well. Has anyone run into this before? -- Mike Johnson Web Developer/Systems Asst. Smarter Living, Inc. phone (617) 497-2500 x226
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
