Why replication provides redundancy in Redis - See It in Action

Understanding Redundancy with Redis Replication

📖 Scenario: You are managing a small online store that uses Redis to store product inventory data. You want to make sure your data is safe even if one Redis server stops working.

🎯 Goal: Build a simple Redis setup with one master and one replica to see how replication creates redundancy and protects your data.

📋 What You'll Learn

Create a Redis master server configuration

Create a Redis replica server configuration that replicates the master

Add a key-value pair to the master

Verify the key exists on the replica to confirm redundancy

💡 Why This Matters

🌍 Real World

Many online services use Redis replication to keep data safe and available even if one server crashes.

💼 Career

Understanding replication and redundancy is important for roles like database administrator, backend developer, and system engineer.

1

Set up Redis master server configuration

Create a Redis configuration file named redis-master.conf with the default settings and specify the port as 6379.

Redis

# Create redis-master.conf with port 6379
# Your code here

Hint

The master server listens on port 6379 by default. Just specify port 6379 in the config file.

2

Set up Redis replica server configuration

Create a Redis configuration file named redis-replica.conf that sets the port to 6380 and configures it to replicate the master at 127.0.0.1 on port 6379 using the replicaof directive.

Redis

port 6379
# Default Redis master configuration

# Create redis-replica.conf with port 6380 and replicaof 127.0.0.1 6379
# Your code here

Hint

Use replicaof 127.0.0.1 6379 to tell the replica where the master is.

3

Add data to the master server

Connect to the Redis master server on port 6379 and add a key called product:1001 with the value "In Stock" using the SET command.

Redis

port 6379
# Default Redis master configuration

port 6380
replicaof 127.0.0.1 6379

# Connect to master and add key product:1001 with value "In Stock"
# Your code here

Hint

Use the Redis command SET product:1001 "In Stock" on the master server.

4

Verify data replication on the replica server

Connect to the Redis replica server on port 6380 and use the GET command to check that the key product:1001 has the value "In Stock", confirming replication and redundancy.

Redis

port 6379
# Default Redis master configuration

port 6380
replicaof 127.0.0.1 6379

# Connect to master and add key product:1001 with value "In Stock"
SET product:1001 "In Stock"

# Connect to replica and verify key product:1001 has value "In Stock"
# Your code here

Hint

Use GET product:1001 on the replica server to confirm the value.

Practice

1. Why does replication in Redis provide redundancy?

easy

A. Because it speeds up data processing by using multiple CPUs

B. Because it copies data to multiple servers to prevent data loss

C. Because it compresses data to save storage space

D. Because it deletes old data to free memory

Solution

1. Step 1: Understand replication purpose

   Replication copies data from the main server to other servers.

2. Step 2: Connect replication to redundancy

   This copying creates backups, so if one server fails, data is not lost.

3. Final Answer:

   Because it copies data to multiple servers to prevent data loss -> Option B

4. Quick Check:

   Replication = Data backup [OK]

Hint: Replication means copying data to keep backups safe [OK]

Common Mistakes:

• Thinking replication speeds up processing
• Confusing replication with data compression
• Believing replication deletes old data

2. Which Redis command is used to set up a replica for redundancy?

easy

A. REPLICA

B. REPLICAOF

C. SLAVEOF

D. SET key value

Solution

1. Step 1: Recall Redis replication command

   The command to make a Redis server a replica is SLAVEOF; REPLICAOF is not a valid Redis command.

2. Step 2: Check options for exact syntax

   SLAVEOF <master-ip> <master-port> is the correct command and syntax.

3. Final Answer:

   SLAVEOF <master-ip> <master-port> -> Option C

4. Quick Check:

   Replica setup command = SLAVEOF [OK]

Hint: Remember replica setup uses SLAVEOF command [OK]

Common Mistakes:

• Using the non-existent REPLICAOF
• Confusing SET with replication commands
• Using REPLICA without OF

3. Given a Redis master with key user:1 set to "Alice", what will a replica show after replication?

medium

A. user:1 = "Alice"

B. user:1 = null

C. user:1 = "Bob"

D. user:1 key will be deleted

Solution

1. Step 1: Understand replication data flow

   The replica copies data from the master, so keys and values match.

2. Step 2: Predict replica key value

   Since master has user:1 = "Alice", replica will have the same.

3. Final Answer:

   user:1 = "Alice" -> Option A

4. Quick Check:

   Replica data = Master data [OK]

Hint: Replica always matches master data after sync [OK]

Common Mistakes:

• Assuming replica has no data initially
• Thinking replica changes values independently
• Believing keys get deleted on replica

4. You set up a Redis replica but it never syncs data from the master. What is the likely error?

medium

A. The master server has no data to replicate

B. The replica server has more memory than the master

C. The replica server is running an older Redis version

D. The replica IP or port is incorrect in the SLAVEOF command

Solution

1. Step 1: Identify common replication setup errors

   Incorrect IP or port in SLAVEOF prevents connection to master.

2. Step 2: Analyze other options

   Master having no data doesn't stop syncing; version mismatch usually warns; memory size difference doesn't block replication.

3. Final Answer:

   The replica IP or port is incorrect in the SLAVEOF command -> Option D

4. Quick Check:

   Wrong master address = no sync [OK]

Hint: Check SLAVEOF IP and port carefully [OK]

Common Mistakes:

• Ignoring connection details in SLAVEOF
• Assuming no data means no replication
• Blaming Redis version without checking logs

5. In a Redis setup, why is having multiple replicas important for redundancy beyond just one replica?

hard

A. Because if one replica fails, others still have the data

B. Because multiple replicas speed up writes to the master

C. Because replicas automatically compress data to save space

D. Because replicas prevent the master from crashing

Solution

1. Step 1: Understand redundancy with multiple replicas

   Multiple replicas mean data is copied to several servers, so failure of one replica doesn't cause data loss.

2. Step 2: Evaluate other options

   Replicas do not speed up writes, compress data, or prevent master crashes directly.

3. Final Answer:

   Because if one replica fails, others still have the data -> Option A

4. Quick Check:

   Multiple replicas = higher data safety [OK]

Hint: More replicas mean safer data if one fails [OK]

Common Mistakes:

• Thinking replicas speed up master writes
• Believing replicas compress data automatically
• Assuming replicas protect master from crashes