Subject: Re: SOLVED: Problem with *very* slow replication, FreeBSD 6.2

Mailing List

Home

Forum Home

MySQL General - General MySQL discussion

MySQL++ - Programming with the C++ API to MySQL

MaxDB - Everything about MaxDB, formerly known as SAP DB

ODBC - ODBC with the MySQL Connector/ODBC driver

MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP

Java Help - Mostly related to the MySQL Connector/J driver

Perl - Perl support for MySQL with DBI and DBD::mysql

GUI - MySQL GUI Tools

Announcement

Subjects

•	Subject: mysql openssl Question
•	ERROR 1045: Access denied for user: 'root@localhost ' (Using password: NO)
•	Update one field with more fields from another table
•	Subject: Getting Identity after INSERT
•	ERROR 2002: Can 't connect to local MySQL server through socket
•	mysql test 4 1 fails with the gis test
•	Subject: MySQL Cluster Software
•	Downgrade Mysql from 4 to 3 23
•	Mysql 4 0 Oracle Stored Procedure Trigger Conversion
•	Can 't access mysql after kernel upgrade
•	Executing MySQL Commands From Within C Program
•	Comparing and writing out BLOBS
•	Subject: Re: Preventing Duplicate Entries
•	FULLTEXT query format question
•	Strange behavior, Table Level Permission
•	Does the binary log enabling affect the MySQL performances?
•	mysql:it 's a db not a dbms how it 's possible?!
•	mysql have same function mthod as Oracle decode()

Subject: Re: SOLVED: Problem with *very* slow replication, FreeBSD 6.2

Subject: Re: SOLVED: Problem with very slow replication, FreeBSD 6.2

2007-11-04 - By Baron Schwartz

Back
Christopher E. Brown wrote:
> On Sat, 3 Nov 2007, bob b wrote:
> So, a slave is down for 8hrs. It comes online and pulls the binlog in
> 120 seconds. The "seconds behind master" does not reflect 8hrs, but how
> many seconds (at current processing rate) before the slave finishes the
> relay logs.
>
>
> The "seconds behind master" value is really "seconds until currency with
> the relay logs" and should prolly be documented as such.

This is incorrect. In most circumstances, it's basically the difference
between the timestamp of the binlog event the SQL thread is currently
processing, and the master's current timestamp (as fetched by the I/O
thread). So it really is what it sounds like: the seconds behind the
master. If it says 100, it means the slave is processing an event that
took place 100 seconds ago on the master.

You can read the source code in show_master_info() in sql/slave.cc.

Baron

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=mysql@(protected)