Index refresh interval in Elasticsearch - Time & Space Complexity

Time Complexity: Index refresh interval

O(n)

Understanding Time Complexity

When working with Elasticsearch, the index refresh interval controls how often new data becomes visible for searching.

We want to understand how changing this interval affects the time it takes for data to appear in search results.

Scenario Under Consideration

Analyze the time complexity of the index refresh operation with this setting.

PUT /my-index/_settings
{
  "index" : {
    "refresh_interval" : "1s"
  }
}

POST /my-index/_doc
{
  "message": "Hello Elasticsearch"
}

GET /my-index/_search
{
  "query": { "match_all": {} }
}
    

This code sets the refresh interval to 1 second, indexes a document, then searches the index.

Identify Repeating Operations

Look at what repeats during index refresh:

• Primary operation: Periodic refresh of the index to make new data searchable.
• How many times: Once every refresh interval (e.g., every 1 second).

How Execution Grows With Input

The refresh operation runs regularly regardless of how many documents are added.

Input Size (n)	Approx. Operations
10 documents	Refresh runs every interval, processing 10 new docs
100 documents	Refresh runs every interval, processing 100 new docs
1000 documents	Refresh runs every interval, processing 1000 new docs

Pattern observation: The cost per refresh grows roughly linearly with the number of new documents since each must be made searchable.

Final Time Complexity

Time Complexity: O(n)

This means the time to refresh grows in direct proportion to the number of new documents waiting to be made searchable.

Common Mistake

[X] Wrong: "The refresh interval time directly controls how fast each refresh operation runs."

[OK] Correct: The interval controls how often refresh happens, not how long each refresh takes. The refresh time depends on how many new documents need processing.

Interview Connect

Understanding how refresh intervals affect indexing and search latency helps you balance speed and resource use in real Elasticsearch setups.

Self-Check

What if we changed the refresh interval from 1 second to 30 seconds? How would the time complexity of each refresh operation change?

Practice

1. What does the index.refresh_interval setting control in Elasticsearch?

easy

A. The number of shards in the index

B. The size limit of the index

C. How often the index makes new data searchable

D. The maximum number of replicas

Solution

1. Step 1: Understand the role of index.refresh_interval

   This setting controls the frequency at which Elasticsearch refreshes the index to make newly indexed data searchable.

2. Step 2: Compare with other options

   The other options relate to the number of shards, size limits, and replicas, which are unrelated to refresh timing.

3. Final Answer:

   How often the index makes new data searchable -> Option C

4. Quick Check:

   Refresh interval = data searchable frequency [OK]

Hint: Refresh interval means how often new data appears [OK]

Common Mistakes:

• Confusing refresh interval with shard count
• Thinking it controls index size
• Mixing it up with replica settings

2. Which of the following is the correct way to set the refresh interval to 5 seconds in an Elasticsearch index settings JSON?

easy

A. { "refresh_interval": 5 }

B. { "index": { "refresh_interval": "5000" } }

C. { "index": { "refresh_interval": 5 } }

D. { "index": { "refresh_interval": "5s" } }

Solution

1. Step 1: Identify correct JSON structure for refresh interval

   The refresh interval must be a string with time units, inside the index object.

2. Step 2: Validate options

   { "index": { "refresh_interval": "5s" } } uses "5s" (5 seconds) correctly as a string with units. Plain numbers like 5 without units are invalid. { "index": { "refresh_interval": "5000" } } uses "5000" without units, which is incorrect. Missing the index object is also invalid.

3. Final Answer:

   { "index": { "refresh_interval": "5s" } } -> Option D

4. Quick Check:

   Refresh interval needs string with units [OK]

Hint: Use string with time unit like "5s" for refresh interval [OK]

Common Mistakes:

• Using number without time unit
• Placing refresh_interval outside index object
• Using milliseconds as plain number string

3. Given the following index setting:

{ "index": { "refresh_interval": "30s" } }

What happens if you index a document and immediately search for it within 10 seconds?

medium

A. The document will not be found until after 30 seconds

B. The document will be found immediately

C. The document will never be found

D. The document will be found after 10 seconds

Solution

1. Step 1: Understand refresh interval effect on search

   With a 30-second refresh interval, Elasticsearch refreshes the index every 30 seconds to make new data searchable.

2. Step 2: Analyze timing of search after indexing

   If you search within 10 seconds, the index has not refreshed yet, so the new document is not visible.

3. Final Answer:

   The document will not be found until after 30 seconds -> Option A

4. Quick Check:

   Refresh interval delays new data visibility [OK]

Hint: Search before refresh interval means no new data visible [OK]

Common Mistakes:

• Assuming instant search visibility
• Confusing refresh interval with indexing speed
• Thinking document is never searchable

4. You set index.refresh_interval to -1 to disable automatic refresh during heavy indexing. After indexing, you want to make all data searchable immediately. What is the correct way to do this?

medium

A. Set index.refresh_interval back to 0

B. Run a manual _refresh API call on the index

C. Restart the Elasticsearch cluster

D. Delete and recreate the index

Solution

1. Step 1: Understand disabling refresh with -1

   Setting refresh_interval to -1 disables automatic refresh, so new data is not searchable until manually refreshed.

2. Step 2: Identify how to make data searchable immediately

   Using the _refresh API triggers an immediate refresh, making all indexed data searchable without restarting or recreating.

3. Final Answer:

   Run a manual _refresh API call on the index -> Option B

4. Quick Check:

   Manual refresh needed when auto refresh disabled [OK]

Hint: Use _refresh API to make data searchable after disabling refresh [OK]

Common Mistakes:

• Setting refresh_interval to 0 instead of calling _refresh
• Restarting cluster unnecessarily
• Deleting index instead of refreshing

5. You have an index with heavy write load and want to optimize indexing speed without losing data visibility for search. Which approach best balances performance and freshness?

hard

A. Set index.refresh_interval to a higher value during indexing, then manually refresh after bulk load

B. Set index.refresh_interval to 0 to refresh after every write

C. Disable refresh permanently by setting index.refresh_interval to -1 and never refresh

D. Delete the index and create a new one for each bulk load

Solution

1. Step 1: Understand trade-off between refresh interval and indexing speed

   Frequent refreshes slow indexing but improve data freshness; less frequent refreshes speed indexing but delay visibility.

2. Step 2: Choose best practice for heavy write load

   Setting a higher refresh interval during bulk indexing reduces refresh overhead, then manually refreshing after bulk load balances speed and search freshness.

3. Final Answer:

   Set index.refresh_interval to a higher value during indexing, then manually refresh after bulk load -> Option A

4. Quick Check:

   Adjust refresh interval for bulk, then manual refresh [OK]

Hint: Increase refresh interval during bulk, refresh manually after [OK]

Common Mistakes:

• Setting refresh_interval to 0 causes slow indexing
• Disabling refresh permanently loses search freshness
• Deleting index wastes resources