Service provider index does not exist as an alias but it should be – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.8-8.9

Briefly, this error occurs when Elasticsearch is trying to access an index through an alias, but the alias does not exist. This could be due to a misconfiguration or a failed index creation process. To resolve this issue, you can either create the missing alias or change the configuration to use the correct alias. Alternatively, you can check if the index exists and if not, create it. Also, ensure that the Elasticsearch cluster is healthy and all nodes are functioning properly.

This guide will help you check for common problems that cause the log ” service provider index [{}] does not exist as an alias; but it should be ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, index.

Log Context

Log “service provider index [{}] does not exist as an alias; but it should be” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    private void logChangedAliasState(IndexAbstraction aliasInfo) {
        if (aliasInfo == null) {
            logger.warn("service provider index/alias [{}] no longer exists"; ALIAS_NAME);
        } else if (aliasInfo.getType() != IndexAbstraction.Type.ALIAS) {
            logger.warn("service provider index [{}] does not exist as an alias; but it should be"; ALIAS_NAME);
        } else if (aliasInfo.getIndices().size() != 1) {
                "service provider alias [{}] refers to multiple indices [{}] - this is unexpected and is likely to cause problems";


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?