How long did the one update statement run?
(A slow update, even if it is a single transaction, can slow down replication.
From: Revathi Rangachari [mailto:masrrev@stripped]
Sent: Monday, April 02, 2012 3:42 PM
Subject: Seconds Behind Master increasing in slave
We have a master-slave setup. The slave acts only as a replicate and does not cater to
any client requests.
Over the last 24 hours there has been more than 4 to 6 hours delay in the replication.
The CPU, IO, memory usage all seem to be under control. I changed the SET GLOBAL
innodb_flush_log_at_trx_commit = 0 ;
The slave sql and io threads are running.
show processlist shows only one update statement on a table.
In spite of all this the slave still lags behind in replication by 5 hours.
Any suggestion to improve the replication performance is highly appreciated.
MySQL Replication Mailing List
For list archives: http://lists.mysql.com/replication
To unsubscribe: http://lists.mysql.com/replication
The information contained in this e-mail and any attached
documents may be privileged, confidential and protected from
disclosure. If you are not the intended recipient you may not
read, copy, distribute or use this information. If you have
received this communication in error, please notify the sender
immediately by replying to this message and then delete it
from your system.