Already exists as alias – Elasticsearch Error How To Solve Related Issues

Already exists as alias – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many errors 


This guide will help you check for common problems that cause the log “already exists as alias” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: metadata, alias, cluster.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

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.

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 ElasticSearch – Reindexing your data with zero downtime -views 7,051 ,score 4

ElasticSearch Create Index, index already exists exception -views   5,247,score 1

Find Configuration Errors

Analyze Now