Shard allocation awareness in Elasticsearch - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable shard allocation awareness for the attribute 'rack'.

Elasticsearch

PUT /_cluster/settings
{
  "transient": {
    "cluster.routing.allocation.awareness.attributes": "[1]"
  }
}

Drag options to blanks, or click blank then click option'

Arack

Bzone

Cnode

Dhost

Attempts:

3 left

💡 Hint

Common Mistakes

Using an attribute name that is not configured on nodes.

Setting the attribute under 'persistent' instead of 'transient' when testing.

The setting cluster.routing.allocation.awareness.attributes should be set to the attribute name you want to use for shard allocation awareness, such as rack.

2fill in blank

medium

Complete the code to set the awareness forced value to 'rack1' for shard allocation.

Elasticsearch

PUT /_cluster/settings
{
  "transient": {
    "cluster.routing.allocation.awareness.force.rack": "[1]"
  }
}

Drag options to blanks, or click blank then click option'

Ahost1

Bzone1

Crack1

Dnode1

Attempts:

3 left

💡 Hint

Common Mistakes

Using an attribute value that does not exist on any node.

Confusing the attribute name with the attribute value.

The forced awareness value should match the attribute value you want to prioritize, such as rack1.

3fill in blank

hard

Fix the error in the code to correctly configure shard allocation awareness for 'zone'.

Elasticsearch

PUT /_cluster/settings
{
  "transient": {
    "cluster.routing.allocation.awareness.attributes": "[1]"
  }
}

Drag options to blanks, or click blank then click option'

A[zone]

B"zone"

C'zone'

Dzone

Attempts:

3 left

💡 Hint

Common Mistakes

Using single quotes instead of double quotes.

Not quoting the string at all.

Using brackets which are invalid here.

The attribute value must be a string enclosed in double quotes in JSON, like "zone".

4fill in blank

hard

Fill both blanks to create a dictionary that sets awareness attributes and forces allocation to 'zone1'.

Elasticsearch

PUT /_cluster/settings
{
  "transient": {
    "cluster.routing.allocation.awareness.attributes": "[1]",
    "cluster.routing.allocation.awareness.force.[2]": "zone1"
  }
}

Drag options to blanks, or click blank then click option'

Azone

Brack

Dhost

Attempts:

3 left

💡 Hint

Common Mistakes

Using different attribute names for the two settings.

Misspelling the attribute name.

The attribute name must be consistent for both settings. Here, zone is used for awareness attributes and for the forced allocation key.

5fill in blank

hard

Fill all three blanks to create a shard allocation awareness setting that uses 'rack' attribute, forces allocation to 'rack2', and sets a custom attribute.

Elasticsearch

PUT /_cluster/settings
{
  "transient": {
    "cluster.routing.allocation.awareness.attributes": "[1]",
    "cluster.routing.allocation.awareness.force.[2]": "[3]"
  }
}

Drag options to blanks, or click blank then click option'

Arack

Crack2

Dzone

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatching attribute names.

Using an invalid forced value.

The attribute name rack is used for awareness and forced allocation, and the forced value is rack2.

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