" Big cleanup in replication code (less logging, better error messages, etc..)
I have been having periodic problems with lost connections with my 4.0.2 slave and master. No errors, other than lost connection, retrying etc. But sometimes the connection doesn't come back even though show slave status indicates that the slave is still running. A slave stop, slave start gets things going again. But I was wondering if these changes mentioned above would help me in any way, and would I be able to benifit from them just by upgrading my slave machine? Thanks, Eric below is a bit of my error log I am using InnoDB.. 021015 14:06:44 InnoDB: Out of memory in additional memory pool. InnoDB: InnoDB will start allocating memory from the OS. InnoDB: You may get better performance if you configure a bigger InnoDB: value in the MySQL my.cnf file for InnoDB: innodb_additional_mem_pool_size. 021016 8:41:12 Error reading packet from server: (server_errno=1159) 021016 8:41:12 Slave I/O thread killed while reading event 021016 8:41:12 Slave I/O thread exiting, read up to log 'www200-bin.008', position 7684721 021016 8:41:12 Error reading relay log event: slave SQL thread was killed 021016 8:41:12 Slave SQL thread exiting, replication stopped in log 'www200-bin.008' at position 7684721 021016 8:41:15 Slave SQL thread initialized, starting replication in log 'www200-bin.008' at position 7684721, relay log './s142-17-103-3-relay-bin.047' position: 1034333 021016 8:41:15 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'www200-bin.008' at position 7684721 021016 17:17:51 Error reading packet from server: (server_errno=1159) 021016 17:17:51 Slave I/O thread killed while reading event 021016 17:17:51 Slave I/O thread exiting, read up to log 'www200-bin.008', position 8248472 021016 17:17:51 Error reading relay log event: slave SQL thread was killed 021016 17:17:51 Slave SQL thread exiting, replication stopped in log 'www200-bin.008' at position 8248472 021016 17:17:54 Slave SQL thread initialized, starting replication in log 'www200-bin.008' at position 8248472, relay log './s142-17-103-3-relay-bin.047' position: 1598084 021016 17:17:54 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'www200-bin.008' at position 8248472 021016 22:36:47 Error reading packet from server: Lost connection to MySQL server during query (server_errno=2013) 021016 22:36:47 Slave I/O thread: Failed reading log event, reconnecting to retry, log 'www200-bin.008' position 8481953 021016 22:36:47 Slave: connected to master '[EMAIL PROTECTED]:3306',replication resumed in log 'www200-bin.008' at position 8481953 % (250) 655 - 9513 (PST Time Zone) "Inquiry is fatal to certainty." -- Will Durant --------------------------------------------------------------------- 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
