Read-only replicas in Redis - Time & Space Complexity

Time Complexity: Read-only replicas

O(n)

Understanding Time Complexity

When using read-only replicas in Redis, it's important to understand how the time to get data changes as the amount of data grows.

We want to know how fast reading data from replicas happens as we ask for more data.

Scenario Under Consideration

Analyze the time complexity of the following Redis commands on a read-only replica.

READONLY
GET user:1001
GET user:1002
GET user:1003
...
GET user:n
    

This code sets the connection to read-only mode and then reads multiple user keys from the replica.

Identify Repeating Operations

Look at what repeats when reading from the replica.

• Primary operation: Each GET command reads one key from the replica.
• How many times: Once per key requested, so n times for n keys.

How Execution Grows With Input

Each key read takes about the same time, so more keys mean more total time.

Input Size (n)	Approx. Operations
10	10 GET operations
100	100 GET operations
1000	1000 GET operations

Pattern observation: The total work grows directly with the number of keys read.

Final Time Complexity

Time Complexity: O(n)

This means the time to read keys from the replica grows in a straight line as you ask for more keys.

Common Mistake

[X] Wrong: "Reading from a replica is instant no matter how many keys I ask for."

[OK] Correct: Each key read still takes time, so asking for more keys means more total time.

Interview Connect

Understanding how reading from replicas scales helps you explain system behavior clearly and shows you know how data size affects performance.

Self-Check

"What if we used pipelining to send all GET commands at once? How would the time complexity change?"

Practice

1. What is the main purpose of a read-only replica in Redis?

easy

A. To handle write requests and update the master

B. To copy data from the master and handle read requests

C. To delete data from the master server

D. To act as a backup that does not sync data

Solution

1. Step 1: Understand the role of read-only replicas

   Read-only replicas copy data from the master Redis server and serve read requests to reduce load on the master.

2. Step 2: Identify the correct purpose

   They do not handle writes or delete data; their main job is to share read load.

3. Final Answer:

   To copy data from the master and handle read requests -> Option B

4. Quick Check:

   Read-only replicas = copy data + read requests [OK]

Hint: Replicas copy data and serve reads, not writes [OK]

Common Mistakes:

• Thinking replicas handle writes
• Believing replicas delete data
• Assuming replicas do not sync data

2. Which Redis command is used to configure a server as a read-only replica of another?

easy

A. SETREPLICA <port>

B. COPYFROM <port>

C. SYNCREPLICA <port>

D. REPLICAOF <port>

Solution

1. Step 1: Recall the correct Redis command for replication

   The command to set a Redis server as a replica is REPLICAOF followed by the master's IP and port.

2. Step 2: Verify other options

   Other commands like SETREPLICA, COPYFROM, SYNCREPLICA do not exist in Redis.

3. Final Answer:

   REPLICAOF <master-ip> <port> -> Option D

4. Quick Check:

   Replica setup command = REPLICAOF [OK]

Hint: Use REPLICAOF to set or remove replication [OK]

Common Mistakes:

• Using non-existent commands
• Confusing REPLICAOF with SYNC commands
• Misspelling the command name

3. Given a Redis replica configured with REPLICAOF 192.168.1.10 6379, what happens if you try to run SET key value on the replica?

medium

A. An error occurs because replicas are read-only

B. The key is set successfully on the replica

C. The command is forwarded to the master automatically

D. The replica disconnects from the master

Solution

1. Step 1: Understand replica behavior on write commands

   Redis replicas are read-only and reject write commands like SET.

2. Step 2: Identify the outcome of running SET on a replica

   Running SET on a replica causes an error because it cannot accept writes.

3. Final Answer:

   An error occurs because replicas are read-only -> Option A

4. Quick Check:

   Write commands on replicas = error [OK]

Hint: Replicas reject writes, only master accepts them [OK]

Common Mistakes:

• Assuming writes succeed on replicas
• Thinking commands auto-forward to master
• Believing replica disconnects on write

4. You configured a Redis replica with REPLICAOF 192.168.1.10 6379 but it is not syncing data. What is the most likely cause?

medium

A. The replica command should be REPLICA instead of REPLICAOF

B. The replica server is running an older Redis version

C. The master IP or port is incorrect

D. The master server is set as a replica itself

Solution

1. Step 1: Check configuration details

   If the replica is not syncing, the most common cause is incorrect master IP or port in the REPLICAOF command.

2. Step 2: Evaluate other options

   Older Redis versions may cause issues but less likely; REPLICAOF is the correct command; master being a replica can cause sync issues but less common.

3. Final Answer:

   The master IP or port is incorrect -> Option C

4. Quick Check:

   Incorrect master address = no sync [OK]

Hint: Verify master IP and port carefully [OK]

Common Mistakes:

• Using wrong command name
• Ignoring IP/port typos
• Assuming version mismatch is always cause

5. You want to temporarily stop replication on a Redis replica without shutting it down. Which command should you use?

hard

A. REPLICAOF NO ONE

B. REPLICAOF NONE

C. STOPREPLICA

D. DISABLEREPLICA

Solution

1. Step 1: Recall how to remove replication

   To stop replication temporarily, use REPLICAOF NO ONE which makes the replica a standalone server.

2. Step 2: Check other options

   Commands like REPLICAOF NONE, STOPREPLICA, DISABLEREPLICA do not exist in Redis.

3. Final Answer:

   REPLICAOF NO ONE -> Option A

4. Quick Check:

   Stop replication = REPLICAOF NO ONE [OK]

Hint: Use REPLICAOF NO ONE to stop replication temporarily [OK]

Common Mistakes:

• Using incorrect command variants
• Trying to shut down replica to stop replication
• Confusing NO ONE with NONE