Reader small image

You're reading from  Learning Elasticsearch

Product typeBook
Published inJun 2017
PublisherPackt
ISBN-139781787128453
Edition1st Edition
Right arrow
Author (1)
Abhishek Andhavarapu
Abhishek Andhavarapu
author image
Abhishek Andhavarapu

Abhishek Andhavarapu is a software engineer at eBay who enjoys working on highly scalable distributed systems. He has a master's degree in Distributed Computing and has worked on multiple enterprise Elasticsearch applications, which are currently serving hundreds of millions of requests per day. He began his journey with Elasticsearch in 2012 to build an analytics engine to power dashboards and quickly realized that Elasticsearch is like nothing out there for search and analytics. He has been a strong advocate since then and wrote this book to share the practical knowledge he gained along the way.
Read more about Abhishek Andhavarapu

Right arrow

Elasticsearch server logs

The server logs should be the go-to place when you are trying to figure out why a node is not starting or why shards are not being allocated. The logs provide insight into what's wrong. Elasticsearch uses log4j to handle the logging. The logs are written to the following:

ES_HOME/logs/cluster_name.log

By default, the logs are rotated every day. If you look at the logs directory, you should find something like this:



In the preceding example, the cluster name is es-dev. The current logs are written to es-dev.log. If you want to change the default log level, you can do so using the cluster setting API as shown next. In the following command, we are changing the logging level for the root logger. Elasticsearch also supports changing the log level for a single module-like discovery:

PUT /_cluster/settings
{
"transient": {
"logger...
lock icon
The rest of the page is locked
Previous PageNext Page
You have been reading a chapter from
Learning Elasticsearch
Published in: Jun 2017Publisher: PacktISBN-13: 9781787128453

Author (1)

author image
Abhishek Andhavarapu

Abhishek Andhavarapu is a software engineer at eBay who enjoys working on highly scalable distributed systems. He has a master's degree in Distributed Computing and has worked on multiple enterprise Elasticsearch applications, which are currently serving hundreds of millions of requests per day. He began his journey with Elasticsearch in 2012 to build an analytics engine to power dashboards and quickly realized that Elasticsearch is like nothing out there for search and analytics. He has been a strong advocate since then and wrote this book to share the practical knowledge he gained along the way.
Read more about Abhishek Andhavarapu