Node roles (master, data, ingest) in Elasticsearch - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the role of a master node in Elasticsearch?

A master node manages the cluster by keeping track of all nodes, creating or deleting indices, and managing cluster-wide settings. It ensures the cluster is healthy and balanced.

beginner

What does a data node do in Elasticsearch?

A data node stores the actual data and executes data-related operations like search and aggregation. It handles indexing and querying of documents.

intermediate

Explain the purpose of an ingest node in Elasticsearch.

An ingest node processes incoming documents before indexing. It can transform or enrich data using pipelines, like adding fields or removing unwanted data.

intermediate

Can a single Elasticsearch node have multiple roles? If yes, give an example.

Yes, a single node can have multiple roles. For example, a node can be both a master and a data node, handling cluster management and storing data simultaneously.

advanced

Why is it important to separate master nodes from data nodes in large Elasticsearch clusters?

Separating master and data nodes improves stability and performance. Master nodes focus on cluster management without being slowed by heavy data operations, while data nodes handle storage and queries.

Which Elasticsearch node is responsible for managing cluster state and metadata?

A Client node

B Data node

C Master node

D Ingest node

The master node manages cluster state and metadata, ensuring the cluster is healthy.

What role does a data node play in Elasticsearch?

A Routes requests without storing data

B Processes incoming documents before indexing

C Manages cluster settings

D Stores data and executes search queries

Data nodes store data and handle search and aggregation operations.

Which node type uses pipelines to transform documents before indexing?

A Ingest node

B Data node

C Master node

D Coordinating node

Ingest nodes use pipelines to process and transform documents before they are indexed.

Is it possible for a node to be both a master and a data node?

A No, nodes can only have one role

B Yes, nodes can have multiple roles

C Only in Elasticsearch 7.x

D Only if configured as a coordinating node

Nodes can have multiple roles, such as master and data, depending on configuration.

Why might you separate master nodes from data nodes in a cluster?

A To improve cluster stability and performance

B To reduce network traffic

C To allow ingest pipelines to run faster

D To enable faster backups

Separating master and data nodes helps keep cluster management stable and improves overall performance.

Describe the three main Elasticsearch node roles: master, data, and ingest.

Think about what each node does in the cluster lifecycle.

Explain why you might want to assign multiple roles to a single Elasticsearch node.

Consider cluster size and resource availability.

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