Synchronization process in Redis - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the main purpose of Redis synchronization process?

Redis uses synchronization to keep data consistent between the master and replicas. What is the main goal of this synchronization?

A To backup data to an external storage system

B To compress data for faster network transfer

C To ensure replicas have the same data as the master at all times

D To encrypt data between clients and server

💡 Hint

Think about why replicas exist in Redis.

The synchronization process ensures that replicas have the same data as the master so they can serve read requests and provide fault tolerance.

❓ query_result

intermediate

What output does the command INFO replication show during synchronization?

When you run INFO replication on a Redis replica during synchronization, what key information will you see?

A The master link status and the offset of data synced

B The list of all keys in the database

C The number of connected clients

D The current CPU usage of the Redis server

💡 Hint

Look for synchronization status details in the replication info.

The INFO replication command shows the master link status and the replication offset, which indicate synchronization progress.

📝 Syntax

advanced

Which Redis command triggers a full synchronization from master to replica?

Choose the command that forces the master to send a full data snapshot to the replica for synchronization.

A BGSAVE

B PSYNC

C SAVE

D SYNC

💡 Hint

This command is used when the replica has no previous data or lost connection.

The SYNC command triggers a full synchronization by sending a snapshot of the entire dataset to the replica.

❓ optimization

advanced

How can Redis minimize data transfer during synchronization after a temporary disconnection?

Redis supports partial resynchronization to reduce data sent after a brief disconnection. Which mechanism enables this optimization?

A Using RDB snapshots only

B PSYNC command with replication offset tracking

C Disabling persistence to speed up sync

D Compressing data with LZF before transfer

💡 Hint

Look for a command that resumes sync from where it left off.

The PSYNC command allows partial resynchronization by sending only the missing data since the last offset, reducing bandwidth.

🔧 Debug

expert

What response occurs if a Redis replica cannot complete partial synchronization due to a mismatch in replication IDs?

During partial resynchronization, if the replica's replication ID does not match the master's, what response will the master send?

A "FULLRESYNC <replid> <offset>" response forcing full sync

B "LOADING Redis is loading the dataset" error

C "WRONGTYPE Operation against a key holding the wrong kind of value" error

D "OOM command not allowed" error due to memory limits

💡 Hint

Think about what happens when partial sync cannot continue.

If replication IDs mismatch, Redis cannot do partial sync and responds with a "FULLRESYNC " response, forcing a full synchronization.

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