You're reading from Getting Started with Elastic Stack 8.0 Run powerful and scalable data platforms to search, observe, and secure your organization

Product type Paperback

Published in Mar 2022

Publisher Packt

ISBN-13 9781800569492

Length 474 pages

Edition 1st Edition

Tools

Elasticsearch

Concepts

Enterprise Search

Author (1):

Asjad Athick

View More author details

Table of Contents (18) Chapters

Preface

1. Section 1: Core Components

2. Chapter 1: Introduction to the Elastic Stack FREE CHAPTER

3. Chapter 2: Installing and Running the Elastic Stack

4. Section 2: Working with the Elastic Stack

5. Chapter 3: Indexing and Searching for Data

6. Chapter 4: Leveraging Insights and Managing Data on Elasticsearch

7. Chapter 5: Running Machine Learning Jobs on Elasticsearch

8. Chapter 6: Collecting and Shipping Data with Beats

9. Chapter 7: Using Logstash to Extract, Transform, and Load Data

10. Chapter 8: Interacting with Your Data on Kibana

11. Chapter 9: Managing Data Onboarding with Elastic Agent

12. Section 3: Building Solutions with the Elastic Stack

13. Chapter 10: Building Search Experiences Using the Elastic Stack

14. Chapter 11: Observing Applications and Infrastructure Using the Elastic Stack

15. Chapter 12: Security Threat Detection and Response Using the Elastic Stack

16. Chapter 13: Architecting Workloads on the Elastic Stack

17. Other Books You May Enjoy

Elasticsearch nodes

An Elasticsearch node is a single running instance of Elasticsearch. A single physical or virtual machine can run multiple instances or nodes of Elasticsearch, assuming it has sufficient resources to do so.

Elasticsearch nodes perform a variety of roles within the cluster. The roles that a node performs can be granularly controlled as required.

We will cover some common node roles in the following sections.

Master-eligible nodes

Master-eligible nodes take part in the master election process. At any point in time, a single node is elected to be the active master. The active master node keeps track of other nodes in the cluster, creation or deletion of indices, shards being allocated to nodes based on requirements/constraints, cluster settings being applied, and more.

The master role is generally not very resource-intensive and can be co-located on a node running other roles in smaller clusters. Running the master role on a dedicated host makes sense...