Cluster architecture in Redis - Time & Space Complexity

Time Complexity: Cluster architecture

O(1)

Understanding Time Complexity

When using Redis cluster architecture, it is important to understand how the time to complete operations changes as the cluster grows.

We want to know how the number of nodes affects the speed of commands across the cluster.

Scenario Under Consideration

Analyze the time complexity of accessing a key in a Redis cluster.

# Client sends command to cluster
# Cluster uses hash slot to find node
# Node executes command locally
# Result returned to client

# Example:
GET mykey
    

This snippet shows a simple key lookup in a Redis cluster, where the cluster routes the command to the correct node based on the key.

Identify Repeating Operations

Look for repeated steps that affect time.

• Primary operation: Hash slot calculation and node lookup.
• How many times: Once per command to find the right node.

How Execution Grows With Input

As the number of nodes increases, the cluster must find the right node for the key.

Number of Nodes (n)	Approx. Operations
3	1 hash calculation + 1 node lookup
10	1 hash calculation + 1 node lookup
100	1 hash calculation + 1 node lookup

Pattern observation: The number of operations stays about the same regardless of cluster size because the hash slot calculation is constant time and node lookup is direct.

Final Time Complexity

Time Complexity: O(1)

This means the time to find and access a key in the cluster does not grow as the cluster gets bigger.

Common Mistake

[X] Wrong: "More nodes means slower key lookups because the cluster has to check many nodes."

[OK] Correct: The cluster uses a fixed hash slot to directly find the node, so it does not check nodes one by one.

Interview Connect

Understanding how Redis cluster keeps key lookups fast helps you explain distributed system design clearly and confidently.

Self-Check

What if the cluster used a linear search to find the node instead of a hash slot? How would the time complexity change?

Practice

1.

What is the main purpose of Redis Cluster architecture?

easy

A. To backup data to external storage every minute

B. To store data only on a single server for simplicity

C. To encrypt data automatically on all nodes

D. To split data across multiple servers for better performance and fault tolerance

Solution

1. Step 1: Understand Redis Cluster design

   Redis Cluster splits data across multiple servers using hash slots to distribute load.

2. Step 2: Identify the main benefit

   This splitting improves speed, storage capacity, and fault tolerance by avoiding a single point of failure.

3. Final Answer:

   To split data across multiple servers for better performance and fault tolerance -> Option D

4. Quick Check:

   Redis Cluster = Data distribution + fault tolerance [OK]

Hint: Redis Cluster splits data for speed and safety [OK]

Common Mistakes:

• Thinking Redis Cluster stores data on one server
• Confusing cluster with encryption feature
• Assuming cluster only handles backups

2.

Which command line option is required to start a Redis node with cluster enabled?

redis-server --port 7000 --cluster-enabled ???

easy

A. yes

B. true

C. on

D. enable

Solution

1. Step 1: Recall Redis cluster start syntax

   To enable cluster mode, the option is --cluster-enabled yes.

2. Step 2: Confirm correct boolean value

   Redis expects 'yes' or 'no' for this flag, not 'true', 'on', or 'enable'.

3. Final Answer:

   yes -> Option A

4. Quick Check:

   Cluster enabled flag = yes [OK]

Hint: Use 'yes' to enable cluster mode in Redis [OK]

Common Mistakes:

• Using 'true' or 'on' instead of 'yes'
• Typing 'enable' which is invalid
• Omitting the cluster-enabled option

3.

Given a Redis Cluster with 3 nodes, each handling 5461 hash slots, what happens if one node fails?

Choose the correct behavior:

medium

A. All data on the failed node is lost permanently

B. The cluster stops working until the failed node is back

C. The cluster continues working if replicas exist for the failed node's slots

D. The cluster automatically merges all slots to remaining nodes

Solution

1. Step 1: Understand Redis Cluster fault tolerance

   Redis Cluster uses replicas to provide fault tolerance. If a node fails, replicas can take over its hash slots.

2. Step 2: Analyze failure impact

   If replicas exist, the cluster continues working by promoting replicas. Without replicas, cluster availability is affected.

3. Final Answer:

   The cluster continues working if replicas exist for the failed node's slots -> Option C

4. Quick Check:

   Node failure + replicas = cluster stays up [OK]

Hint: Replicas keep cluster alive if a node fails [OK]

Common Mistakes:

• Assuming cluster stops immediately on node failure
• Thinking data is lost without replicas
• Believing cluster merges slots automatically

4.

Identify the error in this Redis cluster node start command:

redis-server --port 7001 --cluster-enabled yes --cluster-config-file nodes-7001.conf --cluster-node-timeout 5000 --cluster-announce-ip 192.168.1.10 --cluster-announce-port 7001 --cluster-announce-bus-port 17001 --cluster-enabled no

medium

A. The command has conflicting cluster-enabled flags

B. The port number is invalid

C. The cluster-config-file name is incorrect

D. The cluster-node-timeout value is too low

Solution

1. Step 1: Review cluster-enabled flags

   The command has two --cluster-enabled flags: one set to 'yes' and another to 'no'. This is conflicting.

2. Step 2: Understand impact of conflicting flags

   Redis will use the last flag, disabling cluster mode, which contradicts other cluster options.

3. Final Answer:

   The command has conflicting cluster-enabled flags -> Option A

4. Quick Check:

   Conflicting flags cause cluster mode error [OK]

Hint: Avoid multiple cluster-enabled flags in one command [OK]

Common Mistakes:

• Ignoring repeated flags causing conflicts
• Assuming port 7001 is invalid
• Thinking config file name causes error

5.

You want to create a Redis Cluster with 6 nodes: 3 masters and 3 replicas. Which of the following is the correct approach to assign hash slots and replicas?

hard

A. Assign all hash slots to replicas only; masters hold no slots

B. Assign all 16384 hash slots evenly to 3 masters; assign each replica to a different master node

C. Assign hash slots randomly to all 6 nodes without replicas

D. Assign hash slots only to one master; others act as replicas

Solution

1. Step 1: Understand hash slot distribution

   Redis Cluster has 16384 hash slots. These should be evenly split among master nodes for balanced load.

2. Step 2: Assign replicas properly

   Each replica should be linked to a different master to provide fault tolerance and avoid single points of failure.

3. Final Answer:

   Assign all 16384 hash slots evenly to 3 masters; assign each replica to a different master node -> Option B

4. Quick Check:

   Slots evenly on masters + replicas assigned = correct cluster setup [OK]

Hint: Distribute slots evenly on masters; assign replicas per master [OK]

Common Mistakes:

• Assigning slots to replicas instead of masters
• Not linking replicas to masters
• Putting all slots on one master only