List:General Discussion« Previous MessageNext Message »
From:Johan De Meersman Date:October 11 2012 12:43pm
Subject:Re: innodb_lock_wait_timeout
View as plain text  
----- Original Message -----
> From: "Markus Falb" <markus.falb@stripped>
> But why is retrying better than raising the value?
> So what is better, adjusting the timeout or retrying application side
> and why?

Well, raising the timeout would probably help, but may cause more concurrent connections
to stay open until they block the server.

The idea of retrying is that everything you've done before that particular transaction has
already been committed, so you (probably) can't easily undo it. A retry gives you a chance
to still finish what you were doing with no other loss than some time waiting. Regardless
of how many retries fail, you will still be in the same position as you were when the
first attempt failed.

Linux Bier Wanderung 2012, now also available in Belgium!
August, 12 to 19, Diksmuide, Belgium -
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