Scheduling next run for updating cluster info in – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.9

Briefly, this error occurs when Elasticsearch is trying to schedule the next run for updating cluster information. This is not necessarily an error, but more of an informational message indicating that the system is working as expected. However, if you’re seeing this message too frequently, it could indicate that your cluster is not stable or is undergoing many changes. To resolve this, you could consider optimizing your cluster configuration, reducing the number of changes, or increasing the cluster update interval.

This guide will help you check for common problems that cause the log ” Scheduling next run for updating cluster info in: {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster.

Log Context

Log “Scheduling next run for updating cluster info in: {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    try {
                    } finally { //schedule again after we refreshed
                        if (isMaster) {
                            if (logger.isTraceEnabled()) {
                                logger.trace("Scheduling next run for updating cluster info in: {}"; updateFrequency.toString());
                            threadPool.scheduleUnlessShuttingDown(updateFrequency; executorName(); this);


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?