Reader small image

You're reading from  Monitoring Elasticsearch

Product typeBook
Published inJul 2016
PublisherPackt
ISBN-139781784397807
Edition1st Edition
Right arrow
Authors (3):
Dan Noble
Dan Noble
author image
Dan Noble

About the Author Dan is a software engineer with a passion for writing secure, clean, and articulate code. He enjoys working with a variety of programming languages and software frameworks, particularly Python, Elasticsearch, and frontend technologies. Dan currently works on geospatial web applications and data processing systems. Dan has been a user and advocate of Elasticsearch since 2011. He has given talks about Elasticsearch at various meetup groups, and is the author of the Python Elasticsearch client “rawes.” Dan was also a technical editor for the Elasticsearch Cookbook, Second Edition, by Alberto Paro (ISBN: 1783554835). Acknowledgements I would like to thank my beautiful wife, Julie, for putting up with me while I wrote this book. Thanks for supporting me every step of the way. I would also like to thank my friends and colleagues James Cubeta, Joe McMahon, and Mahmoud Lababidi, who shared their insight, time, and support. I would like to give a special thanks to Abe Usher – you have been an incredible mentor over the years. Finally, thanks to everyone at Packt Publishing for helping to make this book happen. A special thanks to Merint Mathew, Sonali Vernekar, Husain Kanchwala, and Amey Varangaonkar for your valuable and careful feedback.
Read more about Dan Noble

View More author details
Right arrow

Diagnosing problems


Elasticsearch node failures can manifest in many different ways. Some of the symptoms of node failures are as follows:

  • A node crashes during heavy data indexing

  • Elasticsearch process stops running for an unknown reason

  • A cluster won't recover from a yellow or red state

  • Query requests time out

  • Index requests time out

When a node in your cluster experiences problems such as these, it can be tempting to just restart Elasticsearch or the node itself and move on like nothing happened. However, without addressing the underlying issue, the problem is likely to resurface in the future. If you encounter scenarios such as the ones just listed, check the health of your cluster in the following manner:

  • Check the cluster health with Elasticsearch-head or Kopf

  • Check the historical health with Marvel

  • Check for Nagios alerts

  • Check Elasticsearch log files

  • Check system log files

  • Check the system health using command-line tools

These steps will help diagnose the root cause of problems in your cluster...

lock icon
The rest of the page is locked
Previous PageNext Page
You have been reading a chapter from
Monitoring Elasticsearch
Published in: Jul 2016Publisher: PacktISBN-13: 9781784397807

Authors (3)

author image
Dan Noble

About the Author Dan is a software engineer with a passion for writing secure, clean, and articulate code. He enjoys working with a variety of programming languages and software frameworks, particularly Python, Elasticsearch, and frontend technologies. Dan currently works on geospatial web applications and data processing systems. Dan has been a user and advocate of Elasticsearch since 2011. He has given talks about Elasticsearch at various meetup groups, and is the author of the Python Elasticsearch client “rawes.” Dan was also a technical editor for the Elasticsearch Cookbook, Second Edition, by Alberto Paro (ISBN: 1783554835). Acknowledgements I would like to thank my beautiful wife, Julie, for putting up with me while I wrote this book. Thanks for supporting me every step of the way. I would also like to thank my friends and colleagues James Cubeta, Joe McMahon, and Mahmoud Lababidi, who shared their insight, time, and support. I would like to give a special thanks to Abe Usher – you have been an incredible mentor over the years. Finally, thanks to everyone at Packt Publishing for helping to make this book happen. A special thanks to Merint Mathew, Sonali Vernekar, Husain Kanchwala, and Amey Varangaonkar for your valuable and careful feedback.
Read more about Dan Noble