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

Opster Team

Aug-23, Version: 7.5-7.15

Briefly, this error occurs when Elasticsearch takes longer than the set threshold to write the cluster state. This could be due to high load, insufficient resources, or network issues. To resolve this, you can optimize your cluster by reducing the number of shards, increasing resources, or improving network connectivity. Additionally, consider adjusting the warning threshold if it’s set too low for your environment’s performance capabilities.

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 Elasticsearch concepts: cluster, threshold.

Log Context

Log “writing cluster state took [{}ms] which is above the warn threshold of [{}]; ” classname is PersistedClusterStateService.java.
We extracted the following from Elasticsearch 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";