List:General Discussion« Previous MessageNext Message »
From:Steven Staples Date:March 26 2010 2:45pm
Subject:MySQL Slave is almost 1 day behind
View as plain text  
Good day :)

We've had our master/slave server running for a while now, and just
yesterday, we started getting behind.
Not entirely sure what happened, but it is getting further and furhter

(master server)
mysql> show master status\G
*************************** 1. row ***************************
            File: mysql-bin.000280
        Position: 58090245
    Binlog_Do_DB: admin_server,baf,freeradius,radius
1 row in set (0.00 sec)

(slave server)
mysql> show slave status\G
*************************** 1. row ***************************
             Slave_IO_State: Waiting for master to send event
                Master_User: slave_user
                Master_Port: 3306
              Connect_Retry: 60
            Master_Log_File: mysql-bin.000280
        Read_Master_Log_Pos: 55208258
             Relay_Log_File: backup-relay-bin.000530
              Relay_Log_Pos: 96663109
      Relay_Master_Log_File: mysql-bin.000259
           Slave_IO_Running: Yes
          Slave_SQL_Running: Yes
            Replicate_Do_DB: admin_server,baf,freeradius,radius
                 Last_Errno: 0
               Skip_Counter: 0
        Exec_Master_Log_Pos: 96662972
            Relay_Log_Space: 2211376614
            Until_Condition: None
              Until_Log_Pos: 0
         Master_SSL_Allowed: No
      Seconds_Behind_Master: 77473
1 row in set (0.00 sec)

Now, we are logging the freeradius packets into mysql, and like I said, it
has been running fine, up until yesterday.   Any idea how the slave would
get this far behind, and not be generating any errors?

It is my understanding, that the slave only does update/insert/delete
queries, so even if there was a lot of "select" queries on the master, the
slave wouldn't see them.  We are not running any queries on the slave (it
was set up for backup purposes, so we could stop the slave and backup
completely), and we haven't done a backup on the slave in a couple of days
(yeah, i know... bad bad) so there is really no reason for this.

Can anyone help/assist/point me in the right direction to figure out how to
catch the slave back up to the master?  The master is not being overloaded,
it is keeping up no problem, and the backup server is 8x the server than the
application server, so it shoulnd't even be an i/o or cpu issue.

Please help! :)

Thanks in advance
Steven Staples

MySQL Slave is almost 1 day behindSteven Staples26 Mar
  • Re: MySQL Slave is almost 1 day behindJim Lyons26 Mar
    • Re: MySQL Slave is almost 1 day behindAnanda Kumar26 Mar