Cluster, node, and shard architecture in Elasticsearch - Time & Space Complexity

Time Complexity: Cluster, node, and shard architecture

O(n)

Understanding Time Complexity

When working with Elasticsearch, it is important to understand how the cluster, nodes, and shards affect performance.

We want to know how the time to search or index data grows as the cluster size or shard count increases.

Scenario Under Consideration

Analyze the time complexity of querying data spread across shards in a cluster.

GET /my_index/_search
{
  "query": {
    "match": { "field": "value" }
  }
}
    

This query searches across all shards of the index distributed on multiple nodes in the cluster.

Identify Repeating Operations

Look at what repeats when the query runs:

• Primary operation: Each shard runs the query independently.
• How many times: Once per shard in the index.

How Execution Grows With Input

As the number of shards grows, the query runs on more pieces of data separately.

Input Size (shards)	Approx. Operations
10	10 query runs
100	100 query runs
1000	1000 query runs

Pattern observation: The total work grows linearly with the number of shards.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete the query grows directly with the number of shards involved.

Common Mistake

[X] Wrong: "Adding more shards always makes queries faster because work is split."

[OK] Correct: More shards mean more separate queries to run and combine, which can increase total time.

Interview Connect

Understanding how Elasticsearch splits work helps you explain performance trade-offs clearly and shows you know how distributed systems behave.

Self-Check

"What if we changed the number of replicas per shard? How would that affect the time complexity of queries?"

Practice

1. What is a node in Elasticsearch cluster architecture?

easy

A. A single machine that is part of the cluster

B. A group of machines working together

C. A piece of data stored in the index

D. A backup copy of data

Solution

1. Step 1: Understand the definition of a node

   A node is one machine or server that joins the Elasticsearch cluster to share work.

2. Step 2: Differentiate node from cluster and shard

   A cluster is many nodes working together; shards are parts of data inside nodes.

3. Final Answer:

   A single machine that is part of the cluster -> Option A

4. Quick Check:

   Node = single machine [OK]

Hint: Node means one machine in the cluster [OK]

Common Mistakes:

• Confusing node with cluster
• Thinking node is a data piece
• Mixing node with shard

2. Which of the following is the correct way to describe a shard in Elasticsearch?

easy

A. A part of an index that stores data

B. A node in the cluster

C. A full copy of the entire index

D. A cluster of nodes

Solution

1. Step 1: Define what a shard is

   A shard is a smaller piece or partition of an index that holds part of the data.

2. Step 2: Compare with other options

   It is not a full copy (that's a replica), not a node or cluster.

3. Final Answer:

   A part of an index that stores data -> Option A

4. Quick Check:

   Shard = index part [OK]

Hint: Shard means a data part of an index [OK]

Common Mistakes:

• Thinking shard is a full index copy
• Confusing shard with node
• Mixing shard with cluster

3. Consider an Elasticsearch cluster with 3 nodes and an index configured with 5 primary shards and 1 replica per shard. How many total shards will be in the cluster?

medium

A. 5 shards

B. 10 shards

C. 6 shards

D. 15 shards

Solution

1. Step 1: Calculate total shards per primary and replica

   Each primary shard has 1 replica, so total shards = primary shards + replicas = 5 + 5 = 10 shards.

2. Step 2: Understand shard distribution across nodes

   Since there are 3 nodes, shards are distributed but total shards remain 10. However, the question asks total shards in cluster, including replicas.

3. Step 3: Re-check options

   15 shards says 15 shards, which is incorrect. The correct total is 10 shards.

4. Final Answer:

   10 shards -> Option B

5. Quick Check:

   Total shards = primary + replica = 5 + 5 = 10 [OK]

Hint: Total shards = primary shards x (1 + replicas) [OK]

Common Mistakes:

• Counting only primary shards
• Adding nodes to shard count incorrectly
• Confusing replicas with nodes

4. You have an Elasticsearch cluster with 2 nodes and an index with 4 primary shards and 1 replica. You try to assign 2 replicas per shard. What is the problem with this configuration?

medium

A. Replicas must be zero for cluster to work

B. Primary shards must be equal to replica shards

C. Number of nodes must be equal to number of shards

D. You cannot have more replicas than nodes minus one

Solution

1. Step 1: Understand replica shard limits

   Replicas cannot exceed the number of nodes minus one because replicas cannot be on the same node as primary.

2. Step 2: Apply to given cluster

   With 2 nodes, max replicas per shard = 1 (2 - 1). Trying 2 replicas is invalid.

3. Final Answer:

   You cannot have more replicas than nodes minus one -> Option D

4. Quick Check:

   Replicas ≤ nodes - 1 [OK]

Hint: Replicas max = nodes minus one [OK]

Common Mistakes:

• Setting replicas more than nodes - 1
• Confusing primary and replica counts
• Assuming replicas can be zero always

5. You want to design an Elasticsearch cluster for high availability with 4 nodes. You plan to create an index with 6 primary shards and 2 replicas per shard. What is the best shard and replica configuration to avoid shard allocation errors?

hard

A. 6 primary shards and 3 replicas per shard, total 24 shards

B. 6 primary shards and 2 replicas per shard, total 18 shards

C. 6 primary shards and 1 replica per shard, total 12 shards

D. 4 primary shards and 2 replicas per shard, total 12 shards

Solution

1. Step 1: Check replica limit based on nodes

   With 4 nodes, max replicas per shard = nodes - 1 = 3. So 2 replicas is allowed.

2. Step 2: Consider shard allocation rules

   Each shard copy must be on a different node. 6 primary shards + 2 replicas = 18 shards total, but 18 shards on 4 nodes means some nodes hold multiple shards.

3. Step 3: Avoid allocation errors by balancing shards

   Too many shards per node can cause performance issues. 1 replica (total 12 shards) is safer and avoids errors.

4. Final Answer:

   6 primary shards and 1 replica per shard, total 12 shards -> Option C

5. Quick Check:

   Replicas ≤ nodes - 1 and balanced shards [OK]

Hint: Replicas max = nodes - 1; balance shards per node [OK]

Common Mistakes:

• Setting replicas more than nodes - 1
• Ignoring shard distribution limits
• Choosing fewer shards than needed