Already exists as alias – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

Briefly, this error occurs when you try to create an alias with a name that is already in use by another alias or used by another index as index name
. Aliases in Elasticsearch must have unique names, so you will need to choose a different name for the new alias.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” already exists as alias ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: metadata, alias and cluster.


Log Context

Log “already exists as alias”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (state.metadata().hasIndex(index)) {
 throw new ResourceAlreadyExistsException(state.metadata().index(index).getIndex());
 if (state.metadata().hasAlias(index)) {
 throw new InvalidIndexNameException(index; "already exists as alias");
 * Validates (if this index has a dot-prefixed name) whether it follows the rules for dot-prefixed indices.


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content