From: Markus Falb Date: October 12 2012 2:08pm Subject: innodb_lock_wait_timeout and replication List-Archive: http://lists.mysql.com/mysql/228380 Message-Id: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig193796B70A27A33C03B6C52B" --------------enig193796B70A27A33C03B6C52B Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 =2E.. # Query_time: 52 Lock_time: 0 Rows_sent: 0 Rows_examined: 0 =2E.. 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? --=20 Kind Regards, Markus Falb --------------enig193796B70A27A33C03B6C52B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlB4JGsACgkQYoWFBIJE9eVDDwCfTpahtTQxMZ7qjuDXS/U+P97g h48An2AeWh9Yp3axlOB524Yc8Rg0BDXw =tX18 -----END PGP SIGNATURE----- --------------enig193796B70A27A33C03B6C52B--