%s %s failed to update snapshot upgrader task to started – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.3-8.9

Briefly, this error occurs when Elasticsearch fails to update the status of a snapshot upgrader task to “started”. This could be due to a variety of reasons such as insufficient permissions, network issues, or a problem with the snapshot itself. To resolve this issue, you can try the following: 1) Check and ensure the user has the necessary permissions to perform the task. 2) Verify the network connectivity between the nodes. 3) Check the integrity of the snapshot and try to recreate it if necessary. 4) Restart the Elasticsearch service.

This guide will help you check for common problems that cause the log ” [%s] [%s] failed to update snapshot upgrader task to started ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, task, snapshot.

Log Context

Log “[%s] [%s] failed to update snapshot upgrader task to started” classname is JobModelSnapshotUpgrader.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                        // executor has a single processing queue.
                        (aVoid; e) -> threadPool.executor(UTILITY_THREAD_POOL_NAME).execute(() -> shutdown(e))
                    logger.debug("[{}] [{}] asked for state to be persisted"; jobId; snapshotId);
                }; f -> {
                    logger.error(() -> format("[%s] [%s] failed to update snapshot upgrader task to started"; jobId; snapshotId); f);
                        new ElasticsearchStatusException(
                            "Failed to start snapshot upgrade [{}] for job [{}]";