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

Opster Team

Aug-23, Version: 1-2.9

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 OpenSearch tries to initiate a monitor check while another one is already in progress. This is a built-in mechanism to prevent overlapping checks which could lead to performance issues. To resolve this, you can either wait for the current check to complete before initiating a new one, or adjust the frequency of your monitor checks to reduce the likelihood of overlap. Additionally, ensure that your checks are not taking too long to complete, as this could also lead to overlapping checks.

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 ” 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 OpenSearch concepts: routing, cluster, monitor, allocation.

Log Context

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

    public void onNewInfo(ClusterInfo info) {
        // 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");

        final Map usages = info.getNodeLeastAvailableDiskUsages();
        if (usages == null) {


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