From: Markus Falb
Date: October 11 2012 11:29am
Subject: innodb_lock_wait_timeout
List-Archive: http://lists.mysql.com/mysql/228367
Message-Id: <k56aie$in0$1@ger.gmane.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig8DA96310CCCEE16AF1462149"

--------------enig8DA96310CCCEE16AF1462149
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

I have mostly myisam tables, only a few central used tables are innodb
to avoid table locks. The innodb tables are used like myisam tables e.g.
no explicit transactions.

I encountered a error
MySQL Error: Lock wait timeout exceeded; try restarting transaction
MySQL Error No: 1205

My question is not what caused this timeout but how to handle it.

Should I raise innodb_lock_wait_timeout? What are the disadvantages?
What would be a sensible value?

Should I retry application side?
http://dev.mysql.com/doc/refman/5.0/en/innodb-error-handling.html
says

=2E..snip
Both deadlocks and lock wait timeouts are normal on busy servers and it
is necessary for applications to be aware that they may happen and
handle them by retrying.
snap...

But why is retrying better than raising the value?

So what is better, adjusting the timeout or retrying application side
and why?
--=20
Kind Regards, Markus Falb


--------------enig8DA96310CCCEE16AF1462149
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/

iEYEARECAAYFAlB2rY8ACgkQYoWFBIJE9eX+6gCfVjoiWDzbyi5swUoOwI/wbjRf
yiYAoKFhJHrw/O+rK6moSuC1EOLs2Fqj
=NPEj
-----END PGP SIGNATURE-----

--------------enig8DA96310CCCEE16AF1462149--