Index refresh interval in Elasticsearch - Step-by-Step Execution

Concept Flow - Index refresh interval

Index receives new data

↓

Data stored in memory (translog)

↓

Wait for refresh interval timer

↓

Refresh triggered

↓

In-memory data made searchable

↓

New data visible in search results

↓

Wait for next refresh interval

New data is first stored in memory, then after the refresh interval, it becomes searchable.

Execution Sample

Elasticsearch

PUT /my_index/_settings
{
  "index.refresh_interval": "5s"
}

Sets the index refresh interval to 5 seconds, controlling how often new data becomes searchable.

Execution Table

Step	Action	Refresh Interval Timer	Data State	Search Visibility
1	Index receives new document	Timer starts	Data in memory (not searchable)	No
2	Wait 3 seconds	Timer counting down (2s left)	Data still in memory	No
3	Wait 2 more seconds	Timer reaches 0	Data refreshed	Yes
4	New data visible in search	Timer resets to 5s	Data searchable	Yes
5	Index receives another document	Timer running	New data in memory	No
6	Wait 5 seconds	Timer reaches 0	Data refreshed	Yes
7	New data visible in search	Timer resets	Data searchable	Yes
8	Stop	N/A	N/A	N/A

💡 Process repeats every refresh interval; stops here for demonstration.

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 5	After Step 6	Final
Refresh Interval Timer	5s	5s (started)	0s (refresh triggered)	5s (started again)	0s (refresh triggered)	5s (ready for next)
Data State	No data	In memory (not searchable)	Refreshed (searchable)	In memory (new data)	Refreshed (searchable)	Searchable
Search Visibility	No	No	Yes	No	Yes	Yes

Key Moments - 3 Insights

Why is new data not immediately searchable after indexing?

Because data is first stored in memory and only becomes searchable after the refresh interval timer reaches zero, as shown in execution_table rows 1 and 3.

What happens when the refresh interval timer reaches zero?

The in-memory data is refreshed and made searchable, as seen in execution_table row 3 where Search Visibility changes from No to Yes.

Does the refresh interval timer reset after each refresh?

Yes, the timer resets to the configured interval after each refresh, shown in execution_table rows 4 and 7.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the data become searchable for the first time?

A Step 1

B Step 5

C Step 3

D Step 6

💡 Hint

Check the 'Search Visibility' column in execution_table rows.

According to variable_tracker, what is the value of the Refresh Interval Timer after Step 5?

A 5s

B 0s

C 3s

D N/A

💡 Hint

Look at the 'Refresh Interval Timer' row in variable_tracker after Step 5.

If the refresh interval is set to 10s instead of 5s, how would the timer values change in the execution_table?

A Timer would count down from 5s as before

B Timer would count down from 10s instead of 5s

C Timer would reset to 0s immediately

D Timer would stop running

💡 Hint

Consider the meaning of the refresh interval setting shown in execution_sample.

Concept Snapshot

Index refresh interval controls how often Elasticsearch makes new data searchable.
Data is first stored in memory, then refreshed at intervals (default 1s).
Setting a longer interval reduces overhead but delays search visibility.
Use PUT /index/_settings with "index.refresh_interval" to change it.
Example: "index.refresh_interval": "5s" means refresh every 5 seconds.

Full Transcript

The index refresh interval in Elasticsearch determines how often new data becomes visible in search results. When data is indexed, it is first stored in memory and not immediately searchable. A timer counts down the refresh interval, and when it reaches zero, Elasticsearch refreshes the index, making the new data searchable. This process repeats continuously. Setting a longer refresh interval reduces system load but delays when new data appears in searches. You can change the refresh interval using the index settings API, for example setting it to 5 seconds. The execution table shows the timer counting down and data state changes step by step, while the variable tracker records the timer and data visibility states. Key moments clarify why data isn't searchable immediately and how the timer resets after each refresh. The visual quiz tests understanding of these steps and timer behavior.