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

Opster Team

Aug-23, Version: 6.8-6.8

Briefly, this error occurs when Elasticsearch is unable to read the local state, often due to corruption or deletion of the data directory. This can happen due to disk issues, abrupt system shutdown, or manual deletion. To resolve this, you can try restoring from a backup, if available. If not, you may need to delete the corrupted data directory and restart Elasticsearch, but this will result in data loss. Another option is to try repairing the corrupted files, but this requires advanced knowledge and may not always be successful.

This guide will help you check for common problems that cause the log ” failed to read local state; exiting… ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

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

                long startNS = System.nanoTime();
                logger.debug("took {} to load state"; TimeValue.timeValueMillis(TimeValue.nsecToMSec(System.nanoTime() - startNS)));
            } catch (Exception e) {
                logger.error("failed to read local state; exiting..."; e);
                throw e;