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 Check-Up which can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content