Sending start upgrade request – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.11-8.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 Elasticsearch operation.

Briefly, this error occurs when Elasticsearch is trying to upgrade an index but encounters an issue. This could be due to insufficient disk space, incompatible index version, or network connectivity issues. To resolve this, ensure you have enough disk space and that your index version is compatible with the current Elasticsearch version. If the problem persists, check your network connectivity. Also, consider reindexing your data if the index is outdated or corrupted.

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 ” [{}] [{}] sending start upgrade request ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, upgrade, request.

Log Context

Log “[{}] [{}] sending start upgrade request” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


        // Start job task
        ActionListener configIndexMappingUpdaterListener = ActionListener.wrap(_unused -> {
  "[{}] [{}] sending start upgrade request"; params.getJobId(); params.getSnapshotId());
                MlTasks.snapshotUpgradeTaskId(params.getJobId(); params.getSnapshotId());


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?