Set too low < 10s - How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when the Elasticsearch timeout setting is set too low, in this case, 10 seconds. This could lead to incomplete operations or queries being terminated prematurely. To resolve this issue, you can increase the timeout setting to a higher value that allows your operations to complete. This can be done by adjusting the ‘timeout’ parameter in your Elasticsearch configuration or in the specific API call. However, be cautious not to set it too high as it may lead to resource hogging and performance issues.

This guide will help you check for common problems that cause the log ” [{}] set too low [{}] (< 10s) " to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster.

Log Context

Log “[{}] set too low [{}] (We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// ClusterInfoService is only enabled if the DiskThresholdDecider is enabled
            Boolean newEnabled = settings.getAsBoolean(DiskThresholdDecider.CLUSTER_ROUTING_ALLOCATION_DISK_THRESHOLD_ENABLED; null);

            if (newUpdateFrequency != null) {
                if (newUpdateFrequency.getMillis()