Writing cluster state took ms which is above the warn threshold of – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 1-1.1

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 the time taken to write the cluster state exceeds the warning threshold. This could be due to heavy load, slow network, or insufficient resources. To resolve this, you can optimize your cluster by reducing the number of shards, increasing resources, or improving network speed. Also, consider reviewing your indexing and search operations to ensure they are not causing unnecessary load. Regular monitoring and maintenance of your OpenSearch cluster can help prevent such issues.

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 ” writing cluster state took [{}ms] which is above the warn threshold of [{}]; ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: threshold, cluster.

Log Context

Log “writing cluster state took [{}ms] which is above the warn threshold of [{}];” classname is PersistedClusterStateService.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :

                commit(currentTerm; clusterState.version());
                fullStateWritten = true;
                final long durationMillis = relativeTimeMillisSupplier.getAsLong() - startTimeMillis;
                final TimeValue finalSlowWriteLoggingThreshold = slowWriteLoggingThresholdSupplier.get();
                if (durationMillis >= finalSlowWriteLoggingThreshold.getMillis()) {
                    logger.warn("writing cluster state took [{}ms] which is above the warn threshold of [{}]; " +
                            "wrote full state with [{}] indices";
                        durationMillis; finalSlowWriteLoggingThreshold; stats.numIndicesUpdated);
                } else {
                    logger.debug("writing cluster state took [{}ms]; " +
                            "wrote full state with [{}] indices";


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