Home/ Questions/Q 124483
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T05:00:27+00:00

I am studying how two-phase commit works across a distributed transaction. It is my

  • 0

I am studying how two-phase commit works across a distributed transaction. It is my understanding that in the last part of the phase the transaction coordinator asks each node whether it is ready to commit. If everyone agreed, then it tells them to go ahead and commit.

What prevents the following failure?

  1. All nodes respond that they are ready to commit
  2. The transaction coordinator tells them to ‘go ahead and commit’ but one of the nodes crashes before receiving this message
  3. All other nodes commit successfully, but now the distributed transaction is corrupt
  4. It is my understanding that when the crashed node comes back, its transaction will have been rolled back (since it never got the commit message)

I am assuming each node is running a normal database that doesn’t know anything about distributed transactions. What did I miss?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Summarizing everyone’s answers:

    1. One cannot use normal databases with distributed transactions. The database must explicitly support a transaction coordinator.

    2. The nodes are not instructed to roll back because some of the nodes have already committed. What happens is that when the crashed node comes back, the transaction coordinator tells it to finish the commit.

    • 0