Re: Slave not getting updates
Posted by:
Rick James
Date: September 09, 2014 11:20AM
> Master_Log_File: mysql-bin.000011
> Relay_Master_Log_File: mysql-bin.000011
> Exec_Master_Log_Pos: 996
> Read_Master_Log_Pos: 996
Those agree, so it is caught up. And 996 is a tiny amount -- you don't seem to be replicating much.Po
Positions in the binlog (on the Master) and the relay-log (on the Slave) do _not_ necessarily match each other.
> Relay_Master_Log_File: mysql-bin.000011
> Relay_Log_File: mysqld-relay-bin.000027
Notice how you have been through 11 binlogs and 27 relay logs. It is as if you are stopping/starting both rather often, with the Slave being restarted more often??
> It's not going fast enough to be usable at the moment.
Please elaborate on why it feels that way.
> though load average is below 10% at the moment
That could be an inefficient SELECT that is not replicating anything. Do this when you think things are busy:
SHOW PROCESSLIST;
Some things that can slow down replication:
* ALTER on a huge table
* UPDATE on a huge table, but with no useful INDEX.
When the Slave is "behind", you are likely to see something like that on its SHOW PROCESSLIST.
What is the network bandwidth between the machines? Ethernet? 100MB?
MySQL can easily ship gigabytes per day.
Subject
Views
Written By
Posted
2503
September 08, 2014 07:37AM
1316
September 08, 2014 09:07AM
Re: Slave not getting updates
1100
September 09, 2014 11:20AM
1127
September 09, 2014 02:48PM
1205
September 09, 2014 04:28PM
1215
September 08, 2014 02:35PM
1438
September 09, 2014 02:26AM
1063
September 09, 2014 10:48AM
1003
September 09, 2014 11:18AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.