Synchronization process in Redis - Time & Space Complexity

Time Complexity: Synchronization process

O(n)

Understanding Time Complexity

When Redis synchronizes data between a master and a replica, it copies data to keep them the same.

We want to know how the time needed grows as the data size grows.

Scenario Under Consideration

Analyze the time complexity of the following Redis synchronization commands.

SYNC
# Master sends full dataset to replica
# Replica receives and loads data
    

This process copies all data from the master to the replica to keep them synchronized.

Identify Repeating Operations

Look for repeated actions in the synchronization.

• Primary operation: Sending each data item from master to replica.
• How many times: Once for every item stored in the database.

How Execution Grows With Input

As the number of data items grows, the time to send all data grows too.

Input Size (n)	Approx. Operations
10	10 data sends
100	100 data sends
1000	1000 data sends

Pattern observation: The time grows directly with the number of data items.

Final Time Complexity

Time Complexity: O(n)

This means the time to synchronize grows in direct proportion to the amount of data.

Common Mistake

[X] Wrong: "Synchronization time stays the same no matter how much data there is."

[OK] Correct: Because every data item must be sent, more data means more time.

Interview Connect

Understanding how synchronization time grows helps you explain system behavior clearly and shows you can think about real-world data handling.

Self-Check

"What if Redis used incremental synchronization instead of full sync? How would the time complexity change?"

Practice

1. What is the main purpose of the Redis synchronization process between master and replica?

easy

A. To keep data the same between master and replica

B. To delete old data from the master

C. To speed up client requests

D. To backup data to an external server

Solution

1. Step 1: Understand synchronization goal

   Synchronization in Redis ensures that the replica has the same data as the master.

2. Step 2: Compare options with synchronization purpose

   Only To keep data the same between master and replica matches the goal of keeping data consistent between master and replica.

3. Final Answer:

   To keep data the same between master and replica -> Option A

4. Quick Check:

   Synchronization = Data consistency [OK]

Hint: Synchronization means data stays the same on master and replica [OK]

Common Mistakes:

• Thinking synchronization deletes data
• Confusing synchronization with backup
• Assuming synchronization speeds up queries

2. Which Redis command initiates a full synchronization from master to replica?

easy

A. REPLCONF

B. SYNC

C. PSYNC

D. SAVE

Solution

1. Step 1: Identify command for full sync

   The SYNC command copies all data from master to replica for full synchronization.

2. Step 2: Differentiate from other commands

   REPLCONF is for replication config, PSYNC is partial sync, SAVE is for persistence, so SYNC is correct.

3. Final Answer:

   SYNC -> Option B

4. Quick Check:

   Full sync command = SYNC [OK]

Hint: SYNC command copies all data from master to replica [OK]

Common Mistakes:

• Confusing PSYNC with full sync
• Using SAVE instead of SYNC
• Thinking REPLCONF triggers data copy

3. Given a Redis master and replica setup, what happens after the replica sends the SYNC command to the master?

medium

A. The replica deletes its data and waits

B. The replica becomes the new master

C. The master stops accepting writes temporarily

D. The master sends all its data to the replica

Solution

1. Step 1: Understand SYNC command effect

   When replica sends SYNC, master sends all its data to replica to copy.

2. Step 2: Check other options for correctness

   Replica does not delete data first, master does not stop writes, and replica does not become master here.

3. Final Answer:

   The master sends all its data to the replica -> Option D

4. Quick Check:

   SYNC triggers full data send from master [OK]

Hint: SYNC means master sends full data to replica [OK]

Common Mistakes:

• Thinking replica deletes data before sync
• Assuming master stops writes during sync
• Confusing roles of master and replica

4. You set up a Redis replica but it never completes synchronization. Which of these is a likely cause?

medium

A. The replica's SYNC command is misspelled

B. The replica is running a different Redis version

C. Network issues prevent data transfer

D. The master has no data to send

Solution

1. Step 1: Analyze synchronization failure reasons

   Network problems can block data transfer, causing sync to never complete.

2. Step 2: Evaluate other options

   SYNC command is fixed in Redis protocol, master always sends data if present, version mismatch usually causes errors but not infinite sync.

3. Final Answer:

   Network issues prevent data transfer -> Option C

4. Quick Check:

   Network problems block sync completion [OK]

Hint: Check network if sync never finishes [OK]

Common Mistakes:

• Assuming command spelling causes sync failure
• Ignoring network connectivity
• Blaming version mismatch without error logs

5. In a Redis cluster, how does the synchronization process handle data consistency when a replica reconnects after a network failure?

hard

A. It performs a partial resynchronization using PSYNC if possible

B. It always performs a full SYNC command regardless of previous state

C. It ignores missed commands and continues normally

D. It requires manual data copy from master to replica

Solution

1. Step 1: Understand reconnection sync in Redis

   Redis tries partial resynchronization (PSYNC) to send only missing data after failure.

2. Step 2: Compare with other options

   Full SYNC is fallback if PSYNC fails, ignoring missed commands causes inconsistency, manual copy is not needed.

3. Final Answer:

   It performs a partial resynchronization using PSYNC if possible -> Option A

4. Quick Check:

   Partial sync (PSYNC) handles reconnection efficiently [OK]

Hint: PSYNC tries partial sync after reconnect to save data transfer [OK]

Common Mistakes:

• Thinking full SYNC always runs after reconnect
• Ignoring partial sync optimization
• Assuming manual copy is required