Node roles (master, data, ingest) in Elasticsearch - Step-by-Step Execution

Concept Flow - Node roles (master, data, ingest)

Start Node

↓

Check Role

↓

Master

↓

Cluster

↓

Coordination

A node starts and checks its assigned role: master manages cluster state, data stores and searches data, ingest processes data pipelines.

Execution Sample

Elasticsearch

node.roles: [master, data, ingest]

# Node starts
# Checks roles
# Performs role-specific tasks

This config sets a node with master, data, and ingest roles; it then performs tasks for each role.

Execution Table

Step	Node Role Checked	Action Taken	Result
1	master	Elects cluster master, manages cluster state	Cluster state updated and stable
2	data	Stores and indexes data, handles search queries	Data stored and searchable
3	ingest	Processes incoming data pipelines	Data transformed before indexing
4	All roles processed	Node runs all assigned roles concurrently	Node fully operational
5	No more roles	Execution ends	Node running with master, data, ingest roles

💡 All assigned roles processed; node is fully operational.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
master_role	false	true (elected master)	true	true	true
data_role	false	false	true (stores data)	true	true
ingest_role	false	false	false	true (processes pipelines)	true

Key Moments - 3 Insights

Why does the node perform multiple roles instead of just one?

Because the node's configuration includes multiple roles (master, data, ingest), it performs all assigned roles concurrently as shown in execution_table rows 1 to 4.

What happens if the node is not assigned the master role?

If the node lacks the master role, it won't manage cluster state or elect a master, so execution_table row 1 would be skipped.

How does the ingest role affect data before storage?

The ingest role processes data pipelines to transform data before indexing, as shown in execution_table row 3.

Visual Quiz - 3 Questions

Look at the execution_table, what action does the node take at Step 2?

A Elects cluster master and manages cluster state

B Processes incoming data pipelines

C Stores and indexes data, handles search queries

D Ends execution

💡 Hint

Refer to execution_table row 2 under 'Action Taken'

At which step does the node process data pipelines?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Check execution_table row 3 for ingest role action

If the node did not have the data role, which step would be missing?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Data role corresponds to storing and indexing data in execution_table row 2

Concept Snapshot

Node roles in Elasticsearch:
- master: manages cluster state and elections
- data: stores and searches data
- ingest: processes data pipelines before indexing
Nodes can have multiple roles simultaneously
Each role triggers specific tasks during node startup

Full Transcript

This visual execution shows how an Elasticsearch node with master, data, and ingest roles starts and performs tasks. First, it checks the master role and manages cluster state. Next, it handles data storage and search as a data node. Then, it processes data pipelines as an ingest node. All roles run concurrently, making the node fully operational. Variables track role activation step-by-step. Key moments clarify why nodes can have multiple roles and how each role affects node behavior. The quiz tests understanding of role actions at each step.