Re: Slave not getting updates

[Rick James]

> 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.