DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • The Curious Case of Dead-End-Lock(Deadlock) | MySql
  • Deadlock-Free Synchronization in Java
  • From Database Changes to Real-Time Actions at Scale: Oracle GoldenGate and Java
  • How (and Why) to Build Dynamic Data Pipelines

Trending

  • Columnar Formats for AI Telemetry: Parquet vs Vortex With DuckDB
  • How Performance Engineers Find and Fix Hidden System Bottlenecks
  • Best of Three Worlds: AI Agents Writing In Rust and Java Beat the C Library
  • A Reference Architecture for Constrained AI-Assisted Design

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Data Engineering
  3. Databases
  4. Deadlock in Databases

Deadlock in Databases

Here's why you need to avoid database deadlock.

By 
Anghel Leonard
DZone Core CORE ·
May. 28, 19 · Presentation
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
8.7K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

From databases perspective, a deadlock is a phenomenon that occurs when two transactions are blocking each other.

Image title

In the figure above, we have a classic deadlock situation. Transaction A (old man transaction) holds a lock to resource A (Dogs), but it doesn't release it until it will acquire a lock to resource B (Cats) that is currently locked by transaction B (young man transaction). In the same time, transaction B (young man transaction) holds a lock to resource B (Cats), but it doesn't release it until it will acquire a lock to resource A (Dogs) that is currently locked by transaction A (old man transaction).

The application (data access layer) is responsible for managing the acquisition of the lock/release in order to avoid deadlocks, and implicitly performance issues. Without application support, you need to rely on the database capability of detecting and solving deadlocks (commonly, by aborting one of the transactions involved in a deadlock).

You may also like Java Persistence Performance Illustrated Guide.

Database Threading

Opinions expressed by DZone contributors are their own.

Related

  • The Curious Case of Dead-End-Lock(Deadlock) | MySql
  • Deadlock-Free Synchronization in Java
  • From Database Changes to Real-Time Actions at Scale: Oracle GoldenGate and Java
  • How (and Why) to Build Dynamic Data Pipelines

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook