Why performance tuning handles growth in Elasticsearch - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the number of shards for an index.

Elasticsearch

PUT /my_index
{
  "settings": {
    "number_of_shards": [1]
  }
}

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

A5

B3

C1

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Setting number_of_shards to 0 causes errors.

Using too many shards can reduce performance.

The default and minimum number of shards is 1, which allows the index to store data and scale properly.

2fill in blank

medium

Complete the code to update the refresh interval for better indexing performance.

Elasticsearch

PUT /my_index/_settings
{
  "index": {
    "refresh_interval": [1]
  }
}

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

A"-1"

B"30s"

C"1s"

D"0s"

Attempts:

3 left

💡 Hint

Common Mistakes

Using "0s" is invalid.

Setting refresh_interval too low can hurt indexing speed.

Setting refresh_interval to "-1" disables automatic refresh, improving indexing speed during heavy writes.

3fill in blank

hard

Fix the error in the query to filter documents by a field value.

Elasticsearch

{
  "query": {
    "term": {
      "status": [1]
    }
  }
}

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

A"active"

Btrue

C"status"

Dactive

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting quotes around string values.

Using field names instead of values.

The term query requires the value to be a string in quotes, like "active".

4fill in blank

hard

Fill both blanks to create a range query filtering documents with age greater than 30.

Elasticsearch

{
  "query": {
    "range": {
      "age": {
        "[1]": [2]
      }
    }
  }
}

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

Agt

B30

Cgte

D25

Attempts:

3 left

💡 Hint

Common Mistakes

Using "gte" includes 30, not strictly greater.

Putting the number in quotes causes errors.

Using "gt" means greater than, and 30 is the value to compare.

5fill in blank

hard

Fill all three blanks to create an aggregation that counts documents per status where count is greater than 5.

Elasticsearch

{
  "aggs": {
    "status_count": {
      "terms": {
        "field": "[1]"
      },
      "aggs": {
        "filtered_count": {
          "bucket_selector": {
            "buckets_path": {
              "count": "_count"
            },
            "script": "params.count [2] [3]"
          }
        }
      }
    }
  }
}

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

Astatus

B>

C5

Dcount

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong field name.

Using >= instead of >.

Putting numbers in quotes in script.

The aggregation groups by the "status" field, then filters buckets where count > 5.

Practice

1. Why is performance tuning important for Elasticsearch as data and users grow?

easy

A. It helps maintain fast search and indexing speeds despite growth.

B. It reduces the amount of data stored permanently.

C. It automatically deletes old data to save space.

D. It changes the Elasticsearch version to a newer one.

Solution

1. Step 1: Understand Elasticsearch growth challenges

   As data and users increase, Elasticsearch can slow down without tuning.

2. Step 2: Identify the role of performance tuning

   Tuning adjusts settings to keep search and indexing fast despite more data and queries.

3. Final Answer:

   It helps maintain fast search and indexing speeds despite growth. -> Option A

4. Quick Check:

   Performance tuning = maintain speed [OK]

Hint: Performance tuning keeps speed steady as data grows [OK]

Common Mistakes:

• Thinking tuning deletes data automatically
• Confusing tuning with upgrading Elasticsearch version
• Assuming tuning reduces stored data size

2. Which of the following is a correct Elasticsearch setting to improve performance during growth?

easy

A. index.max_result_window: 1000000

B. index.refresh_interval: 1s

C. index.number_of_shards: 1

D. index.number_of_replicas: 0

Solution

1. Step 1: Review each setting's effect

   Setting replicas to 0 disables redundancy but can improve indexing speed temporarily.

2. Step 2: Identify correct tuning syntax

   index.number_of_replicas: 0 uses correct syntax and is a common tuning step to improve write performance during growth.

3. Final Answer:

   index.number_of_replicas: 0 -> Option D

4. Quick Check:

   Replica count 0 = faster indexing [OK]

Hint: Replicas 0 speeds indexing during growth [OK]

Common Mistakes:

• Using index.refresh_interval: 1s (default, slows bulk indexing)
• Setting default index.number_of_shards: 1 (limits scaling for growth)
• Setting max_result_window too high causing memory issues

3. Given this Elasticsearch query tuning snippet, what is the expected effect?

{
  "query": {
    "match": { "title": "Elasticsearch" }
  },
  "size": 10,
  "timeout": "2s"
}

medium

A. Returns up to 10 matching documents or times out after 2 seconds.

B. Returns exactly 2 documents matching the query.

C. Returns all matching documents ignoring the size limit.

D. Causes an error because timeout is not a valid parameter.

Solution

1. Step 1: Understand query parameters

   Size limits results to 10 documents; timeout limits query time to 2 seconds.

2. Step 2: Determine expected behavior

   The query returns up to 10 matches but stops if it takes longer than 2 seconds.

3. Final Answer:

   Returns up to 10 matching documents or times out after 2 seconds. -> Option A

4. Quick Check:

   Size 10 + timeout 2s = limited results [OK]

Hint: Size limits hits; timeout limits query time [OK]

Common Mistakes:

• Assuming timeout limits number of results
• Thinking size means minimum results
• Believing timeout causes error

4. You have this Elasticsearch setting in your config:

index.refresh_interval: 1s

But your indexing speed is slow. What is the best fix?

medium

A. Increase index.number_of_replicas to 2 for faster writes.

B. Change index.refresh_interval to -1 during bulk indexing.

C. Set index.refresh_interval to 0 to refresh immediately.

D. Delete old indices to free space.

Solution

1. Step 1: Understand refresh interval impact

   Frequent refreshes slow indexing because Elasticsearch makes data searchable often.

2. Step 2: Apply best practice for bulk indexing

   Setting refresh_interval to -1 disables automatic refresh, speeding bulk indexing.

3. Final Answer:

   Change index.refresh_interval to -1 during bulk indexing. -> Option B

4. Quick Check:

   Disable refresh during bulk = faster indexing [OK]

Hint: Disable refresh during bulk indexing for speed [OK]

Common Mistakes:

• Setting refresh_interval to 0 causes overhead
• Increasing replicas slows writes
• Deleting indices unrelated to refresh issue

5. You want to tune Elasticsearch to handle a sudden growth in user queries without slowing down. Which combined approach is best?

hard

A. Decrease shards, increase replicas, and disable query caching.

B. Keep default settings and add more hardware only.

C. Increase shards, reduce replicas temporarily, and optimize query filters.

D. Disable refresh interval permanently and remove all replicas.

Solution

1. Step 1: Analyze tuning options for growth

   Increasing shards spreads data, reducing replicas speeds indexing, and optimizing queries reduces load.

2. Step 2: Evaluate options for best combined effect

   Increase shards, reduce replicas temporarily, and optimize query filters. This combines these best practices to handle growth efficiently.

3. Final Answer:

   Increase shards, reduce replicas temporarily, and optimize query filters. -> Option C

4. Quick Check:

   Shards + replicas + query tuning = handle growth [OK]

Hint: Combine shards, replicas, and query tuning for growth [OK]

Common Mistakes:

• Disabling refresh permanently harms search freshness
• Ignoring query optimization
• Relying only on hardware without tuning