Failed to write global state – How to solve related issues

Average Read Time

2 Mins

Failed to write global state – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Failed to write global state ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: index.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “{}: failed to write global state” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     private void writeGlobalState(String reason; MetaData metaData) throws Exception {
        logger.trace("{} writing state; reason [{}]"; GLOBAL_STATE_LOG_TYPE; reason);
        try {
            globalStateFormat.write(metaData; metaData.version(); nodeEnv.nodeDataLocations());
        } catch (Throwable ex) {
            logger.warn("{}: failed to write global state"; ex; GLOBAL_STATE_LOG_TYPE);
            throw new IOException("failed to write global state"; ex);

    private MetaData loadState() throws Exception {


Run the Check-Up to get a customized report like this:

Analyze your cluster