Io exception while building store stats – 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 Input/Output (I/O) issue while trying to build ‘store stats’. This could be due to a lack of disk space, file permission issues, or a faulty disk. To resolve this, you can free up disk space, check and correct file permissions, or replace the faulty disk. Additionally, ensure that Elasticsearch has the necessary read/write permissions to access the data directory.

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 ” io exception while building ‘store stats’ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: shard, index.

Log Context

Log “io exception while building ‘store stats'” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 final long reservedBytes = bytesStillToRecover == -1 ? StoreStats.UNKNOWN_RESERVED_BYTES : bytesStillToRecover;
 return store.stats(reservedBytes; LongUnaryOperator.identity());
 } catch (IOException e) {
 failShard("Failing shard because of exception during storeStats"; e);
 throw new ElasticsearchException("io exception while building 'store stats'"; e);
 }  public MergeStats mergeStats() {
 final Engine engine = getEngineOrNull();


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