Book Image

Monitoring Elasticsearch

By : Dan Noble, Pulkit Agrawal, Mahmoud Lababidi
Book Image

Monitoring Elasticsearch

By: Dan Noble, Pulkit Agrawal, Mahmoud Lababidi

Overview of this book

ElasticSearch is a distributed search server similar to Apache Solr with a focus on large datasets, a schema-less setup, and high availability. This schema-free architecture allows ElasticSearch to index and search unstructured content, making it perfectly suited for both small projects and large big data warehouses with petabytes of unstructured data. This book is your toolkit to teach you how to keep your cluster in good health, and show you how to diagnose and treat unexpected issues along the way. You will start by getting introduced to ElasticSearch, and look at some common performance issues that pop up when using the system. You will then see how to install and configure ElasticSearch and the ElasticSearch monitoring plugins. Then, you will proceed to install and use the Marvel dashboard to monitor ElasticSearch. You will find out how to troubleshoot some of the common performance and reliability issues that come up when using ElasticSearch. Finally, you will analyze your cluster’s historical performance, and get to know how to get to the bottom of and recover from system failures. This book will guide you through several monitoring tools, and utilizes real-world cases and dilemmas faced when using ElasticSearch, showing you how to solve them simply, quickly, and cleanly.
Table of Contents (15 chapters)
Monitoring Elasticsearch
About the Author
About the Reviewers

Upgrading Marvel

Marvel can be upgraded on a rolling basis. This means that nodes are upgraded one at a time rather than having to shut down the entire cluster to perform an upgrade. For environments with a monitoring cluster and a production cluster, upgrade Marvel on the monitoring cluster before upgrading it on the production cluster.

To upgrade the Marvel Agent, run these steps on all nodes in the monitoring cluster (in this case, just elasticsearch-marvel-01), then for each node in the production cluster (elasticsearch-node-01, elasticsearch-node-02, and elasticsearch-node-03):

  1. Optional: Disable shard allocation on all nodes.


    Disabling shard allocation will make the upgrade faster because the cluster won't try to reallocate shards to other nodes when the node goes down for an upgrade.

    Run the following command:

    curl -XPUT elasticsearch-host-01:9200/_cluster/settings 
    -d '{
           "transient" : {
               "cluster.routing.allocation.enable" : "none"
  2. Stop Elasticsearch: