Re: innodb_lock_wait_timeout and replication
Am 12.10.2012 19:58, schrieb Hubert de Donnea: > I get all your mails for yearscould you not help me and suppress my name > from your contact what the hell why do people subscribe to a mailing-list without use google to understand what a mailing-list is? http://en.wikipedia.org/wiki/Mailing_list and now read your mail-headers and use the "List-Unsubscribe:" included in every message of any mailing-list on this world before you disgrace yourself more signature.asc Description: OpenPGP digital signature
Re: innodb_lock_wait_timeout and replication
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 < hubertdedon...@hotmail.com> wrote: > I get all your mails for yearscould you not help me and suppress my > name from your contact thanks > > > To: mysql@lists.mysql.com > > From: markus.f...@fasel.at > > 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 > > > >
RE: innodb_lock_wait_timeout and replication
I get all your mails for yearscould you not help me and suppress my name from your contact thanks > To: mysql@lists.mysql.com > From: markus.f...@fasel.at > 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 >
innodb_lock_wait_timeout and replication
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 signature.asc Description: OpenPGP digital signature
