Shard allocation awareness in Elasticsearch - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is shard allocation awareness in Elasticsearch?

Shard allocation awareness is a feature that helps Elasticsearch place shards on different nodes based on specific attributes, like rack or zone, to improve fault tolerance and availability.

beginner

Why is shard allocation awareness important?

It ensures that copies of data (shards) are spread across different physical locations or failure domains, so if one location fails, data remains available from another.

intermediate

How do you configure shard allocation awareness in Elasticsearch?

You set node attributes (like zone or rack) and then configure cluster.routing.allocation.awareness.attributes with those attribute names to tell Elasticsearch to spread shards accordingly.

intermediate

What happens if Elasticsearch cannot satisfy shard allocation awareness rules?

Elasticsearch may delay shard allocation or allocate shards on the same attribute value, risking reduced fault tolerance until the cluster state changes.

beginner

Example: If nodes have attribute zone with values zone1 and zone2, how does shard allocation awareness use this?

Elasticsearch tries to place primary and replica shards on nodes in different zones, so if zone1 fails, data is still available in zone2.

What does shard allocation awareness help prevent?

A More shards per node

B All shard copies being on the same failure domain

C Faster indexing speed

D Automatic data backup to cloud

Shard allocation awareness prevents all copies of a shard from being placed on the same failure domain, like the same rack or zone.

Which Elasticsearch setting controls shard allocation awareness?

A cluster.shard.allocation.awareness

B node.attr.shard.awareness

C index.shard.awareness.enabled

D cluster.routing.allocation.awareness.attributes

The correct setting is cluster.routing.allocation.awareness.attributes, which lists node attributes to consider for shard placement.

If you want to spread shards across data centers, what should you do?

A Increase number of shards

B Disable shard allocation awareness

C Set node attributes for data center and use shard allocation awareness

D Use only one node

You assign node attributes representing data centers and configure shard allocation awareness to spread shards accordingly.

What is a node attribute in Elasticsearch shard allocation awareness?

A A label assigned to a node to group it by physical or logical location

B The number of shards on a node

C The IP address of the node

D The node's CPU speed

Node attributes are labels like 'zone' or 'rack' used to group nodes for shard placement decisions.

What happens if all nodes share the same attribute value in shard allocation awareness?

A Elasticsearch may place all shards on the same attribute value, reducing fault tolerance

B Elasticsearch refuses to allocate shards

C Shards are automatically deleted

D Shard allocation awareness is ignored

If all nodes have the same attribute value, Elasticsearch cannot spread shards across different values, so fault tolerance is reduced.

Explain shard allocation awareness and why it matters in Elasticsearch.

Think about how Elasticsearch keeps data safe across different physical locations.

Describe how to configure shard allocation awareness in an Elasticsearch cluster.

Consider what labels you give nodes and how Elasticsearch uses them.

Practice

1. What is the main purpose of shard allocation awareness in Elasticsearch?

easy

A. To increase the number of shards in an index automatically

B. To compress shard data to save disk space

C. To speed up search queries by caching shards in memory

D. To spread shard copies across different physical locations for better fault tolerance

Solution

1. Step 1: Understand shard allocation awareness concept

   Shard allocation awareness ensures that shard copies are placed on different physical locations like racks or machines.

2. Step 2: Identify the benefit of spreading shards

   This spreading improves fault tolerance by preventing data loss if one location fails.

3. Final Answer:

   To spread shard copies across different physical locations for better fault tolerance -> Option D

4. Quick Check:

   Shard allocation awareness = spreading shards for fault tolerance [OK]

Hint: Think about fault tolerance by spreading data copies [OK]

Common Mistakes:

• Confusing shard allocation awareness with shard count increase
• Thinking it speeds up queries directly
• Assuming it compresses data

2. Which of the following is the correct way to set cluster awareness attributes in Elasticsearch's elasticsearch.yml file?

easy

A. cluster.routing.allocation.awareness.attributes: rack_id

B. cluster.routing.allocation.awareness: rack_id

C. cluster.awareness.routing.allocation.attributes: rack_id

D. routing.allocation.awareness.attributes: rack_id

Solution

1. Step 1: Recall the correct setting syntax

   The correct setting for awareness attributes is cluster.routing.allocation.awareness.attributes.

2. Step 2: Match the option with correct syntax

   cluster.routing.allocation.awareness.attributes: rack_id matches the exact syntax used in Elasticsearch configuration files.

3. Final Answer:

   cluster.routing.allocation.awareness.attributes: rack_id -> Option A

4. Quick Check:

   Correct config key = cluster.routing.allocation.awareness.attributes [OK]

Hint: Look for full correct config key with 'cluster.routing.allocation' [OK]

Common Mistakes:

• Omitting 'cluster.routing' prefix
• Swapping order of words in the key
• Using incomplete or wrong keys

3. Given the following index setting, what will happen when Elasticsearch allocates shards?

{
  "settings": {
    "index.routing.allocation.awareness.include": {
      "rack_id": "rack1,rack2"
    }
  }
}

medium

A. Shards will be allocated only on rack3 nodes

B. Shards will be allocated on any node regardless of rack_id

C. Shards will only be allocated on nodes with rack_id rack1 or rack2

D. Allocation will fail because of invalid syntax

Solution

1. Step 1: Understand the setting meaning

   The setting index.routing.allocation.awareness.include with rack_id values means shards should only go to nodes with those rack_ids.

2. Step 2: Apply to given values

   Since rack1 and rack2 are included, shards will only be allocated on nodes labeled with rack1 or rack2.

3. Final Answer:

   Shards will only be allocated on nodes with rack_id rack1 or rack2 -> Option C

4. Quick Check:

   Allocation include rack1,rack2 = shards on rack1 or rack2 only [OK]

Hint: Include means restrict allocation to listed racks [OK]

Common Mistakes:

• Thinking shards can go to any rack
• Confusing include with exclude
• Assuming syntax error due to JSON format

4. You configured cluster awareness with cluster.routing.allocation.awareness.attributes: rack_id but shards are still allocated on the same rack. What is the likely cause?

medium

A. The index has no replicas configured

B. Nodes do not have the node.attr.rack_id setting defined

C. The cluster is in read-only mode

D. The shards are too large to move

Solution

1. Step 1: Check cluster awareness prerequisites

   For awareness to work, each node must have node.attr.rack_id set to identify its rack.

2. Step 2: Identify missing node attribute effect

   If nodes lack this attribute, Elasticsearch cannot distinguish racks and may place shards on the same rack.

3. Final Answer:

   Nodes do not have the node.attr.rack_id setting defined -> Option B

4. Quick Check:

   Missing node.attr.rack_id = shards not spread by rack [OK]

Hint: Check node attributes match cluster awareness keys [OK]

Common Mistakes:

• Assuming replicas count affects awareness
• Thinking cluster read-only blocks allocation
• Blaming shard size for allocation issues

5. You want to ensure that primary and replica shards are never allocated on the same rack to improve fault tolerance. Which combination of settings achieves this?

hard

A. Set cluster.routing.allocation.awareness.attributes: rack_id and index.routing.allocation.awareness.force.rack_id: true

B. Set cluster.routing.allocation.awareness.attributes: rack_id and index.routing.allocation.awareness.force.rack_id: false

C. Set cluster.routing.allocation.awareness.attributes: rack_id and index.routing.allocation.include.rack_id: rack1,rack2

D. Set cluster.routing.allocation.awareness.attributes: rack_id only

Solution

1. Step 1: Identify setting to enforce shard separation

   The index.routing.allocation.awareness.force.rack_id: true setting forces Elasticsearch to allocate primary and replica shards on different racks.

2. Step 2: Combine with cluster awareness attribute

   Setting cluster.routing.allocation.awareness.attributes: rack_id enables awareness based on rack_id attribute.

3. Step 3: Confirm other options do not enforce separation

   Simply setting the awareness attribute does not force separation. Setting force to false prevents enforcement. Using include settings restricts available racks but does not ensure primary and replica are on different ones.

4. Final Answer:

   Set cluster.routing.allocation.awareness.attributes: rack_id and index.routing.allocation.awareness.force.rack_id: true -> Option A

5. Quick Check:

   Force awareness true + rack_id attribute = shards separated by rack [OK]

Hint: Use force awareness true to separate primary and replica shards [OK]

Common Mistakes:

• Forgetting to set force awareness to true
• Only setting awareness attribute without force
• Confusing include with force settings