List:General Discussion« Previous MessageNext Message »
From:Markus Falb Date:October 11 2012 11:29am
View as plain text  

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?

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.

But why is retrying better than raising the value?

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

Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
innodb_lock_wait_timeoutMarkus Falb11 Oct
  • Re: innodb_lock_wait_timeoutJohan De Meersman11 Oct
    • Re: innodb_lock_wait_timeoutAndrĂ©s Tello11 Oct
      • Re: innodb_lock_wait_timeoutAkshay Suryavanshi11 Oct
        • RE: innodb_lock_wait_timeoutRick James11 Oct
    • Re: innodb_lock_wait_timeoutMarkus Falb12 Oct
      • Re: innodb_lock_wait_timeoutReindl Harald12 Oct
        • Re: innodb_lock_wait_timeoutMichael Dykman12 Oct
      • Re: innodb_lock_wait_timeoutJohan De Meersman15 Oct
  • Re: innodb_lock_wait_timeoutPerrin Harkins11 Oct
Re: innodb_lock_wait_timeoutJohan De Meersman15 Oct