Failed to create empty store – 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 is unable to create an empty store, which is a fundamental part of its data storage system. This could be due to insufficient disk space, incorrect permissions, or a faulty file system. To resolve this issue, you can try freeing up disk space, checking and correcting file permissions, or repairing the file system. If the problem persists, consider reconfiguring your Elasticsearch cluster or reinstalling Elasticsearch.

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 ” failed to create empty store ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repository, plugin.

Log Context

Log “failed to create empty store” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 private static void createEmptyStore(Store store) {
 try {
 } catch (final EngineException | IOException e) {
 throw new IndexShardRecoveryException(store.shardId(); "failed to create empty store"; e);
 } finally {


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?