Distributed transactions and 2PC in DBMS Theory - Time & Space Complexity

Time Complexity: Distributed transactions and 2PC

O(n)

Understanding Time Complexity

Distributed transactions involve coordinating multiple databases to complete a task. Analyzing time complexity helps us understand how the coordination effort grows as more databases join.

We want to know how the time to complete a transaction changes when more participants are involved.

Scenario Under Consideration

Analyze the time complexity of the two-phase commit (2PC) protocol steps.

-- Coordinator sends prepare request to all participants
FOR EACH participant IN participants LOOP
  SEND 'prepare' TO participant;
END LOOP;

-- Participants respond with vote
FOR EACH participant IN participants LOOP
  RECEIVE vote FROM participant;
END LOOP;

-- Coordinator sends commit or abort based on votes
FOR EACH participant IN participants LOOP
  SEND 'commit' OR 'abort' TO participant;
END LOOP;

This code snippet shows the coordinator communicating with each participant in three phases: prepare, vote collection, and final decision.

Identify Repeating Operations

Identify the loops that repeat communication with participants.

• Primary operation: Sending and receiving messages to/from each participant.
• How many times: Each participant is contacted three times (prepare, vote, commit/abort).

How Execution Grows With Input

As the number of participants increases, the total communication steps increase proportionally.

Input Size (n)	Approx. Operations
10	30 messages (3 x 10)
100	300 messages (3 x 100)
1000	3000 messages (3 x 1000)

Pattern observation: The total communication grows linearly as the number of participants increases.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete the transaction grows directly in proportion to the number of participants involved.

Common Mistake

[X] Wrong: "Adding more participants won't affect the transaction time much because messages are sent quickly."

[OK] Correct: Each participant adds extra communication steps, so more participants mean more messages and longer total time.

Interview Connect

Understanding how distributed transactions scale helps you explain coordination costs in real systems. This skill shows you grasp how multiple parts work together and affect performance.

Self-Check

"What if the coordinator could send messages to all participants at the same time? How would that change the time complexity?"

Practice

1. What is the main purpose of the Two-Phase Commit (2PC) protocol in distributed transactions?

easy

A. To ensure all participating systems agree to commit or abort a transaction

B. To speed up transaction processing by skipping checks

C. To allow partial commits in case of failures

D. To encrypt data during transaction processing

Solution

1. Step 1: Understand the role of 2PC in distributed systems

   2PC coordinates multiple systems to either all commit or all abort a transaction, ensuring consistency.

2. Step 2: Analyze the options

   Only To ensure all participating systems agree to commit or abort a transaction correctly describes 2PC's goal of agreement before finalizing changes.

3. Final Answer:

   To ensure all participating systems agree to commit or abort a transaction -> Option A

4. Quick Check:

   2PC ensures agreement = To ensure all participating systems agree to commit or abort a transaction [OK]

Hint: 2PC means all or nothing commit agreement [OK]

Common Mistakes:

• Thinking 2PC speeds up transactions
• Believing partial commits are allowed
• Confusing 2PC with encryption

2. Which of the following is the correct sequence of phases in the Two-Phase Commit protocol?

easy

A. Commit phase followed by Prepare phase

B. Commit phase only

C. Abort phase followed by Prepare phase

D. Prepare phase followed by Commit phase

Solution

1. Step 1: Recall the 2PC phases

   The protocol first asks participants to prepare (vote), then commits if all agree.

2. Step 2: Match phases to options

   Prepare phase followed by Commit phase correctly lists Prepare phase first, then Commit phase.

3. Final Answer:

   Prepare phase followed by Commit phase -> Option D

4. Quick Check:

   2PC phases = Prepare then Commit [OK]

Hint: Prepare before commit in 2PC sequence [OK]

Common Mistakes:

• Reversing the order of phases
• Ignoring the Prepare phase
• Thinking Commit happens alone

3. Consider a distributed transaction using 2PC with three participants: P1, P2, and P3. If P1 and P2 vote to commit but P3 votes to abort during the Prepare phase, what will be the final outcome?

medium

A. Only P1 and P2 commit, P3 aborts

B. All participants abort the transaction

C. All participants commit the transaction

D. Transaction is left in uncertain state

Solution

1. Step 1: Understand voting in 2PC Prepare phase

   All participants must vote to commit for the transaction to proceed; any abort vote causes abort.

2. Step 2: Apply voting results

   Since P3 votes to abort, the coordinator instructs all to abort to keep data consistent.

3. Final Answer:

   All participants abort the transaction -> Option B

4. Quick Check:

   Any abort vote = all abort [OK]

Hint: One abort vote cancels entire transaction [OK]

Common Mistakes:

• Assuming partial commits are allowed
• Thinking transaction stays uncertain
• Ignoring abort votes

4. A distributed transaction using 2PC is stuck indefinitely in the Commit phase. What is the most likely cause of this problem?

medium

A. A participant failed to send its vote during the Prepare phase

B. All participants voted to abort during Prepare phase

C. The coordinator crashed after sending Commit messages but before receiving acknowledgments

D. The transaction was never started

Solution

1. Step 1: Identify causes of blocking in Commit phase

   If the coordinator crashes after sending Commit but before acknowledgments, participants wait indefinitely.

2. Step 2: Analyze options

   The coordinator crashed after sending Commit messages but before receiving acknowledgments matches this scenario; other options relate to earlier phases or no transaction.

3. Final Answer:

   The coordinator crashed after sending Commit messages but before receiving acknowledgments -> Option C

4. Quick Check:

   Coordinator crash during Commit causes blocking [OK]

Hint: Coordinator crash after commit message causes blocking [OK]

Common Mistakes:

• Confusing Prepare phase failures with Commit phase blocking
• Assuming abort votes cause commit blocking
• Ignoring coordinator role

5. In a distributed system using 2PC, how can the protocol be improved to avoid the blocking problem caused by coordinator failure during the Commit phase?

hard

A. Use a Three-Phase Commit protocol that adds a pre-commit phase

B. Skip the Prepare phase to speed up commits

C. Allow participants to commit independently without coordinator

D. Increase the timeout for participant responses

Solution

1. Step 1: Understand blocking in 2PC

   2PC can block if coordinator fails after sending commit but before acknowledgments.

2. Step 2: Identify protocol improvements

   Three-Phase Commit adds a pre-commit phase to reduce blocking by ensuring participants can safely decide without coordinator.

3. Final Answer:

   Use a Three-Phase Commit protocol that adds a pre-commit phase -> Option A

4. Quick Check:

   3PC adds pre-commit to avoid blocking [OK]

Hint: 3PC adds pre-commit phase to prevent blocking [OK]

Common Mistakes:

• Skipping Prepare phase breaks consistency
• Allowing independent commits causes inconsistency
• Just increasing timeout doesn't fix blocking