Failed to read local state started shards exiting – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.7-1.7

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 read the local state of the started shards due to issues like disk I/O errors, file corruption, or insufficient permissions. To resolve this, you can try the following: 1) Check the disk health and replace it if necessary. 2) Verify the file permissions and adjust them accordingly. 3) If the data is corrupted, restore it from a backup. 4) Restart the Elasticsearch node. Always ensure to have a good backup strategy to prevent data loss.

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 read local state (started shards); exiting… ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: shards.

Log Context

Log “failed to read local state (started shards); exiting…” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                long start = System.currentTimeMillis();
                currentState = loadShardsStateInfo();
                logger.debug("took {} to load started shards state"; TimeValue.timeValueMillis(System.currentTimeMillis() - start));
            } catch (Exception e) {
                logger.error("failed to read local state (started shards); exiting..."; e);
                throw e;


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?