JobId Could not retrieve destination index version – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.3-8.9

Briefly, this error occurs when Elasticsearch is unable to fetch the version of the destination index specified in a job. This could be due to the index being deleted, renamed, or inaccessible due to insufficient permissions. To resolve this issue, you can verify the existence and accessibility of the index, check the job’s configuration for any errors, or ensure the user executing the job has the necessary permissions. If the index was deleted or renamed, recreate it or update the job configuration with the correct index name.

This guide will help you check for common problems that cause the log ” [” + jobId + “] Could not retrieve destination index version ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, index, version.

Log Context

Log “[” + jobId + “] Could not retrieve destination index version” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        try {
            Map version = (Map) meta.get(VERSION);
            String createdVersionString = (String) version.get(CREATED);
            return Version.fromString(createdVersionString);
        } catch (Exception e) {
            logger.error(() -> "[" + jobId + "] Could not retrieve destination index version"; e);
            return null;

    public interface Metadata {