also, SHOW SLAVE STATUS \G
Which version of 5.1 ? (There were some performance regressions in
early 5.1 releases.)
On 9/8/11 2:30 PM, Prabhat Kumar wrote:
> please check processlist on slave. might be some things locked..
>
> On Thu, Sep 8, 2011 at 1:54 PM, Chad Morland<cmorland@stripped> wrote:
>
>> I have a new slave server that has MySQL 5.1 on it and I have a 5.0
>> Master server. As I understand it this is a valid setup.
>>
>> It seems as if the 5.1 server's replication is falling far behind the
>> master even though it appears as if replication is functioning
>> properly otherwise. As you can see from the master it is on binlog
>> mysqld-bin.000492 but the slave thinks it is on mysqld-bin.000479.
>>
>> I added this server yesterday and at first it was replicating as
>> expected but sometime between then and now replication has fallen
>> behind.
>>
>> How can I debug this or is there something going on that I am missing?
>>
>> On the master:
>> mysql> show master status;
>> +-------------------+----------+--------------+------------------+
>> | File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
>> +-------------------+----------+--------------+------------------+
>> | mysqld-bin.000492 | 30577992 | | |
>> +-------------------+----------+--------------+------------------+
>>
>> On the slave:
>> Slave_IO_State: Waiting for master to send event
>> ....
>> Master_Log_File: mysqld-bin.000479
>> Read_Master_Log_Pos: 501583254
>> Relay_Log_File: mysqld-relay-bin.000029
>> Relay_Log_Pos: 28558189
>> Relay_Master_Log_File: mysqld-bin.000479
>> Slave_IO_Running: Yes
>> Slave_SQL_Running: Yes
>> ...
>> Last_Errno: 0
>> Last_Error:
>> Skip_Counter: 0
>> Exec_Master_Log_Pos: 501582733
>> Relay_Log_Space: 501583694
>> ...
>> Seconds_Behind_Master: 0
>>
>> --
>> MySQL Replication Mailing List
>> For list archives: http://lists.mysql.com/replication
>> To unsubscribe:
>> http://lists.mysql.com/replication?unsub=1
>>
>>
>
--
Rick James - MySQL Geek
