"Mark T. Dame" <[EMAIL PROTECTED]> wrote: > On 08/11/03 09:03, Jason McCormick wrote: >> >> 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've had similar problems. I've seen this error message as well as: > > Error reading relay log event: Aborting slave SQL thread because of > partial event read > > I've noticed in these cases it appears that the relay log appears > truncated; i.e. the last event in the log appears is incomplete. It > seems to happen more often if there is an unclean shutdown of the slave, > but I've seen it happen in other cases as well (perhaps when MySQL > internally decides to start a new relay log?)
No, MySQL doesn't truncate event when it creates a new relay log. Could you deascribe it more detailed? Which version of MySQL do you use? > > It would be nice if MySQL could be smart enough to reset it's master read > position to that point and reread all the events from that point on > rather than dying and requiring manual intervention. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
