If you are confident that it's not the network, that pretty much leaves RAM or
disk as the source of your problem. Assuming that you are seeing no performance
issues on the master (I expect you would have mentioned), let's focus on the
slave.
The behaviour you describe sounds to me like you
Hey Morgan,
Thanks for the tip. Might come in handy.
But, I'm positive it's not a disconnect / reconnect thing. Or, at least
not one affected by that timeout.
I can do a watch ls -lh in the binlog dir, and see the relay log
increasing in size by a M every 4 or 5 seconds or so. About
I should add that I've turned the SQL thread off, it makes no difference
from what I can see...
On Fri, 20 Jan 2017 10:31:38 -0500
Brad Barnett wrote:
>
>
>
> On Fri, 20 Jan 2017 10:30:09 -0500
> Brad Barnett wrote:
>
> >
> >
> > Hey Morgan,
> >
Hi Brad,
> MySQL community edition 5.6.29, running Linux.
>
> Binlogs never seem to get caught up on slaves.
>
> I've done all I can, to validate that this isn't network or disk related.
>
> Disk tests (using iostat and other methods) show lots of bandwidth left on
> the slave and master.
>
>
Hey all,
I have a weird issue.
MySQL community edition 5.6.29, running Linux.
Binlogs never seem to get caught up on slaves.
I've done all I can, to validate that this isn't network or disk related.
Disk tests (using iostat and other methods) show lots of bandwidth left
on the slave and