List:Replication« Previous MessageNext Message »
From:Eber Duarte Date:April 24 2012 1:01pm
Subject:Re: tracing cause of lag
View as plain text  
Did you try to calculate diff between master and slave binlog positions? Can be a measure
for delay not based on timestamps, that are only updated after statement is finished on
slave host (at least for MySQL version without heart beat).



--- Em dom, 22/4/12, Stanisław Stadnicki <stadnicki@stripped> escreveu:

De: Stanisław Stadnicki <stadnicki@stripped>
Assunto: Re: tracing cause of lag
Para: "ron ramos" <nhadie@stripped>
Cc: "replication@stripped" <replication@stripped>
Data: Domingo, 22 de Abril de 2012, 4:05

Try to run "show full processlist" and check the time of currently executed processes.


Dnia 22 kwi 2012 o godz. 04:53 ron ramos <nhadie@stripped> napisał(a):

> Hi,
> Would it be possible to trace which query cause the lag on the slave?
> I have a script that runs every minute to check the lag,
> I basically have the output of "show slave status" and timestamp and
> how much delay: "Sun Apr 22 04:16:01 SGT 2012  -- Slave Lag: 120"
> would this be possible? thanks in advanced!
> Regards,
> Ron
> -- 
> MySQL Replication Mailing List
> For list archives:
> To unsubscribe:

MySQL Replication Mailing List
For list archives:
To unsubscribe:

tracing cause of lagron ramos22 Apr
  • Re: tracing cause of lagStanisław Stadnicki22 Apr
    • RE: tracing cause of lagRick James23 Apr
    • Re: tracing cause of lagEber Duarte24 Apr
      • Re: tracing cause of lagron ramos24 Apr