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.

Practice

1.

What is the primary role of a master node in Elasticsearch?

easy

A. Manage cluster-wide settings and coordinate nodes

B. Store and manage the actual data

C. Process incoming documents before indexing

D. Serve as a backup node for data recovery

Solution

1. Step 1: Understand node roles in Elasticsearch

   The master node is responsible for managing the cluster state and coordinating nodes.

2. Step 2: Differentiate master from other roles

   Data nodes store data, and ingest nodes process documents. Master nodes handle cluster-wide tasks.

3. Final Answer:

   Manage cluster-wide settings and coordinate nodes -> Option A

4. Quick Check:

   Master node = cluster coordination [OK]

Hint: Master node controls cluster settings and coordination [OK]

Common Mistakes:

• Confusing master node with data node
• Thinking ingest node manages cluster
• Assuming master stores data

2.

Which of the following is the correct way to assign a node as a data node in the elasticsearch.yml configuration file?

node.roles: [ ? ]

easy

A. ["master"]

B. ["data"]

C. ["ingest"]

D. ["coordinating"]

Solution

1. Step 1: Identify the role name for data nodes

   Data nodes are assigned the role "data" in the node.roles setting.

2. Step 2: Match the correct syntax

   The correct syntax uses a list with the string "data" inside square brackets and quotes.

3. Final Answer:

   ["data"] -> Option B

4. Quick Check:

   node.roles: ["data"] assigns data node role [OK]

Hint: Use node.roles: ["data"] to assign data node role [OK]

Common Mistakes:

• Using incorrect role names like "coordinating"
• Omitting quotes around role names
• Assigning master role instead of data

3.

Given this node configuration snippet in elasticsearch.yml:

node.roles: ["master", "ingest"]

Which tasks will this node perform?

medium

A. Only manage cluster state

B. Only process incoming documents

C. Manage cluster state and process incoming documents

D. Store data and manage cluster state

Solution

1. Step 1: Analyze the assigned roles

   The node has roles "master" and "ingest", so it can do both tasks.

2. Step 2: Understand what each role does

   Master manages cluster state; ingest processes incoming documents before indexing.

3. Final Answer:

   Manage cluster state and process incoming documents -> Option C

4. Quick Check:

   Roles master + ingest = cluster + document processing [OK]

Hint: Multiple roles mean combined tasks of those roles [OK]

Common Mistakes:

• Assuming node can only have one role
• Confusing ingest with data node role
• Ignoring master role effects

4.

Look at this elasticsearch.yml snippet:

node.roles: master, data

What is the problem with this configuration?

medium

A. Roles must be listed as a YAML list with brackets and quotes

B. The roles "master" and "data" cannot be assigned together

C. The roles should be uppercase

D. The node.roles setting is deprecated

Solution

1. Step 1: Check YAML syntax for node.roles

   Roles must be defined as a list, e.g., ["master", "data"], not as a comma-separated string.

2. Step 2: Validate role assignment rules

   Assigning master and data roles together is allowed; roles are lowercase; node.roles is valid.

3. Final Answer:

   Roles must be listed as a YAML list with brackets and quotes -> Option A

4. Quick Check:

   YAML list syntax required for node.roles [OK]

Hint: Use YAML list syntax: node.roles: ["master", "data"] [OK]

Common Mistakes:

• Writing roles as comma-separated string without brackets
• Using uppercase role names
• Thinking roles cannot combine

5.

You want to create a node that only processes incoming documents but does not store data or manage cluster state. Which node.roles setting should you use?

hard

A. ["master", "data"]

B. ["data"]

C. ["master"]

D. ["ingest"]

Solution

1. Step 1: Identify the role for processing incoming documents

   The ingest role processes incoming documents before indexing.

2. Step 2: Exclude roles that store data or manage cluster

   Data role stores data; master manages cluster state. We want neither.

3. Final Answer:

   ["ingest"] -> Option D

4. Quick Check:

   Only ingest role processes documents without storing or managing [OK]

Hint: Use node.roles: ["ingest"] for document processing only [OK]

Common Mistakes:

• Choosing data role which stores data
• Choosing master role which manages cluster
• Combining roles unnecessarily