Error reading values – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch encounters an issue while trying to read data from an index or a file. This could be due to a corrupted index, insufficient permissions, or a disk I/O problem. To resolve this issue, you can try the following: 1) Check and repair the corrupted index if any, 2) Ensure that Elasticsearch has the necessary permissions to read the file, 3) Check the health of your disk and fix any I/O issues.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” Error reading values ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search, aggregations.

Log Context

Log “Error reading values” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 protected NumericDocValues getKeys(LeafReaderContext context) {
 try {
 values = valuesSource.bytesValues(context);
 } catch (IOException e) {
 throw new ElasticsearchException("Error reading values"; e);
 return new AbstractNumericDocValues() {  private int docID = -1;


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Get expert answers on Elasticsearch/OpenSearch