Course contentsShow
← Software Engineering
Lesson 918 of 1,93328. Transactions and ConsistencyFree lesson

Lock Timeouts and Wait Strategies

Managing how long transactions wait for locks and handling timeout scenarios gracefully.

Lock Timeouts and Wait Strategies

What you'll learn: How to configure how long transactions wait for locks and handle timeout failures gracefully.

When a transaction tries to acquire a lock held by another transaction, it must decide: wait indefinitely, wait for a specific duration, or fail immediately. This is where lock timeouts and wait strategies come into play.

Understanding Lock Waits

Imagine waiting in line at a busy coffee shop. You could:

  • Wait forever (risky if someone ahead orders 50 lattes)
  • Wait 5 minutes then leave if not served
  • Check if the line is too long and leave immediately

Databases offer similar choices for transactions waiting on locks.

Lock Timeout Configuration

Most databases let you set a maximum wait time before a transaction gives up:

-- PostgreSQL example
SET lock_timeout = '5s';

-- MySQL example  
SET innodb_lock_wait_timeout = 10;

If the lock isn't available within this window, the database raises a timeout error instead of waiting indefinitely.

Wait Strategy Options

Immediate failure (no wait): Fail fast if the lock is held. Useful for read-heavy operations where stale data is acceptable.

Bounded wait: Wait up to X seconds. Balances responsiveness with giving transactions a fair chance.

Unbounded wait: Default in many systems. Risks blocking indefinitely if a long-running transaction holds locks.

Handling Timeouts Gracefully

When a timeout occurs, your application should:

  • Catch the timeout exception
  • Decide whether to retry (with exponential backoff)
  • Log the event for monitoring
  • Return a meaningful error to the user rather than crashing

Proper timeout configuration prevents one slow transaction from cascading delays across your system while giving legitimate operations time to complete.

Key Takeaway: Lock timeouts prevent transactions from waiting indefinitely, and choosing the right wait strategy helps balance responsiveness with system throughput while avoiding cascade failures.