On Tue, Sep 6, 2011 at 6:12 AM, Rob Wultsch wrote:
>> Hm.
>>
>> It seems we have sort of ethernet segment saturation problem.
>
> A possible bandaid/quick fix is turning on compression for mysql replication.
We've had this exact same issue with a dodgy/overused wan link.
If you are going to turn
> Hm.
>
> It seems we have sort of ethernet segment saturation problem.
A possible bandaid/quick fix is turning on compression for mysql replication.
--
Rob Wultsch
wult...@gmail.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.
Alexis Guajardo wrote:
Are the date time set the same on both servers? What upgrade process did you
use?
Alexis Guajardo
Zaynka.com
On Sep 4, 2011, at 12:09 PM, Andrej Pintar wrote:
any warnings in the logs. timeouts. connects. had same thing... just can't
remember what was it.
-> nev
Hi,
Seconds behind master works this way. It displays the value based on the
difference in the relay log's timestamp and the current timestamp on the
slave machine, it is always 0 if you have no relay log events to
process. This means that your bottleneck is the IO thread. Also, if you
monitor sec
Dear List,
I have a Master -> [ Slave 1, Slave 2 ] setup for years.
Last week we've reinstalled the whole setup to: 5.1.58 from: 5.1.54.
The situation is:
the master says: (show master status)
mysql-bin.87 | 974376716
slave says: (show slave status)
Master_Log_File: mysql-bin.87
Re
