From: Andrew Moore Date: October 12 2012 6:01pm Subject: Re: innodb_lock_wait_timeout and replication List-Archive: http://lists.mysql.com/mysql/228384 Message-Id: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=e89a8ff252fa73614504cbe07988 --e89a8ff252fa73614504cbe07988 Content-Type: text/plain; charset=ISO-8859-1 You are subscribed to the MySQL mailing list. You will need to unsubscribe yourself. On Fri, Oct 12, 2012 at 6:58 PM, Hubert de Donnea < hubertdedonnea@stripped> wrote: > I get all your mails for years....could you not help me and suppress my > name from your contact thanks > > > To: mysql@stripped > > From: markus.falb@stripped > > Subject: innodb_lock_wait_timeout and replication > > Date: Fri, 12 Oct 2012 16:08:42 +0200 > > > > I encountered an error > > MySQL Error: Lock wait timeout exceeded; try restarting transaction > > MySQL Error No: 1205 > > > > For this very statement an entry in the binlog was filed > > > > ... > > # Query_time: 52 Lock_time: 0 Rows_sent: 0 Rows_examined: 0 > > ... > > > > Why is there an entry in the binlog if the statement failed? > > If it is in the binlog it will be replicated to a slave and on the slave > > it will succeed (maybe). > > > > Does this mean that a Lock wait timeout exceeded potentially drive the > > slave out of sync? > > -- > > Kind Regards, Markus Falb > > > > --e89a8ff252fa73614504cbe07988--