Failed on closing cluster state writer – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 1-2.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 OpenSearch operation.

Briefly, this error occurs when OpenSearch fails to close the cluster state writer, which is responsible for recording the state of the cluster. This could be due to issues like insufficient disk space, file system errors, or permission issues. To resolve this, you can check if there’s enough disk space and clean up if necessary. Also, verify the file system for any errors and fix them. Lastly, ensure that OpenSearch has the necessary permissions to write to the disk.

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 on closing cluster state writer ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: cluster.

Log Context

Log “failed on closing cluster state writer” classname is
We extracted the following from OpenSearch source code for those seeking an in-depth context :

                .map(writer -> writer.indexWriter)
                .anyMatch(iw -> iw.getTragicException() != null || iw.isOpen() == false)) {
                try {
                } catch (Exception e) {
                    logger.warn("failed on closing cluster state writer"; 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?

Get expert answers on Elasticsearch/OpenSearch