Hello all,
I was wondering if someone could shed some light on this problem I'm
having. I have 3 slave MySQL servers replication from a master
machine. The master machine is running only MySQL while the slave
machines are an Apache + Tomcat + MySQL web service. All slave
machines are precisely identical. I'm running into a situation where
(seemly at random) after a month or two of consistently flawless
performance, just ONE of the slave machines will report the following
error in the .err log:
030807 9:22:35 Error in Log_event::read_log_event():
'Event too big', data_len=1869425764,event_type=114
030807 9:22:35 Error reading relay log event: slave SQL thread
aborted because of I/O error
030807 9:22:35 Could not parse log event entry, check the master
for binlog corruption This may also be a network problem,
or just a bug in the master or slave code.
030807 9:22:35 Error running query, slave SQL thread aborted. Fix
the problem, and restart the slave SQL thread with "SLAVE START".
We stopped at log 'oakpub-bin.002' position 25239274
However the other two slaves are up-to-date on replication with no error
messages and mysqlbinlog output shows no obvious malformed statements.
This problem is not specific to just one machine but has happened on
all 3 slave nodes in the past few months. Trying to restart the slave
process results in the same error. Manually performing the statement
in the binlog works fine and then the slave can be played forward to
the current master logfile location with no problems. I've also tried
deleting the entire database on the slave and recreating everything
with LOAD DATA FROM MASTER and that goes smoothly as well.
I cannot reproduce this behavior as it's intermittent. Any thoughts?
Thanks,
Jason
--
Jason McCormick
Network & Systems Administrator - Lexi-Comp, Inc.
ja*************@lexi.com - 330.656.0239
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/my***********...ie.nctu.edu.tw
