Database Migration Script Deadlocking with Live Application Transactions

System Design Interview•~30 min read•medium

Liquibase/Flyway migration script executing 'ALTER TABLE orders ADD COLUMN flags INT' during active peak traffic.

1. Understand Requirements & Scope

Liquibase/Flyway migration script executing 'ALTER TABLE orders ADD COLUMN flags INT' during active peak traffic. Failure cascade dynamic: 50k Mut. → Row X-Lock → Spinlock Thrash → Deadlock Graph → 💥 DB Freeze.

Functional Requirements:

Operational Invariant: "Database migration scripts must enforce strict, short lock acquisition timeouts (<=5s) to prevent traffic blocking."
Production Hardening: Configure migration sessions with tight lock wait timeouts: 'SET lock_wait_timeout = 5;' in MySQL or 'SET lock_timeout = '5s';' in PostgreSQL. If the lock cannot be acquired in 5s,
Prevent cascading failure by isolating downstream degradation at the ingress boundary.

2. Back-of-the-Envelope Capacity Estimation

• Incident Scenario Baseline: Liquibase/Flyway migration script executing 'ALTER TABLE orders ADD COLUMN flags INT' during active peak traffic.

• Failure Cascade Path: 50k Mut. → Row X-Lock → Spinlock Thrash → Deadlock Graph → 💥 DB Freeze

• Sub-millisecond rejection / shed latency for overloaded requests

3. High-Level Architecture Flow

Configure migration sessions with tight lock wait timeouts: 'SET lock_wait_timeout = 5;' in MySQL or 'SET lock_timeout = '5s';' in PostgreSQL. If the lock cannot be acquired in 5s, the script aborts and retries with backoff rather than blocking traffic. Invariant: "Database migration scripts must enforce strict, short lock acquisition timeouts (<=5s) to prevent traffic blocking."

Ingress → Bounded Admission Controller → Adaptive Concurrency / Queue Gate → Protected Worker Engine; Overload Shed Path → HTTP 429 / Circuit Fallback (<0.1ms).

Fig 1. Architecture data flow and component topology.

4. Production Implementation & Code

// HARDENED: Fast local Bloom filter / Redis revocation list verification
Claims claims = Jwts.parser().setSigningKey(secret).parseClaimsJws(token).getBody();
if (revocationBloomFilter.mightContain(claims.getId()) && redis.exists("revoked:" + claims.getId())) {
    throw new SecurityException("Revoked token access attempt rejected");
}

Hardened Implementation Sequence

Ingress Boundary Defense: Configure migration sessions with tight lock wait timeouts: 'SET lock_wait_timeout = 5;' in MySQL or 'SET lock_timeout = '5s';' in PostgreSQL. If the
Failure Containment: Eliminate unconstrained buffering and propagate physical backpressure.
Invariant Enforcement: Database migration scripts must enforce strict, short lock acquisition timeouts (<=5s) to prevent traffic blocking.

5. Key Decisions & Operational Mitigations

Architectural Decisions & Trade-Offs

•Ingress Admission: Naive unconstrained buffering causes queue bloat and GC exhaustion. Mitigation: Bounded ingress gate with fast non-blocking shedding.
•Resource Strategy: Static capacity allocations collapse under brownouts. Mitigation: Dynamic adaptive limits scaling to real-time physical bounds.
•Outage Impact: Cascading lock convoys and memory saturation. Mitigation: Isolated failure domains keep P99 latency flat and protected.

Operational Hazards & Mitigations

•Cascading Failure: The ALTER TABLE requires an exclusive table lock. It waits for active transactions to complete. Active transactions queue behind the ALTER TABLE lock. The mutual wait causes a database deadlock and aborts production transactions.
•Breakdown Chain: 50k Mut. → Row X-Lock → Spinlock Thrash → Deadlock Graph → 💥 DB Freeze
•Shedding Failure: Without fast rejection at the boundary, queued dead work triggers multi-second GC pauses, CPU thrashing, and cascading 504 Gateway Timeouts.

Interactive Knowledge Check • Question 1 of 3↓

Interactive Practice Quiz•Question 1 of 3

intermediate

Canary vs Blue-Green Release Strategies

What is the key advantage of Canary Deployments over Blue-Green Deployments for large-scale microservice clusters?