Skipping monitor as a check is already in progress – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.3-8.9

Briefly, this error occurs when Elasticsearch is trying to run a health check or monitor, but a similar process is already running. This is a built-in mechanism to prevent resource overuse. It’s not necessarily a problem unless it’s happening frequently, which could indicate that your checks are taking too long. To resolve this, you can optimize your Elasticsearch cluster to perform checks faster, increase the interval between checks, or reduce the number of checks. Also, ensure that your system has sufficient resources to handle these operations.

This guide will help you check for common problems that cause the log ” skipping monitor as a check is already in progress ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: monitor, routing, allocation, cluster.

Log Context

Log “skipping monitor as a check is already in progress” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


        // TODO find a better way to limit concurrent updates (and potential associated reroutes) while allowing tests to ensure that
        // all ClusterInfo updates are processed and never ignored
        if (checkInProgress.compareAndSet(false; true) == false) {
  "skipping monitor as a check is already in progress");

        if (diskThresholdSettings.isEnabled() == false) {


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?