Unknown alias name was passed to alias Filter – 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 ” Unknown alias name was passed to alias Filter ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: filter, search and alias.

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 “Unknown alias name was passed to alias Filter”classname  is ShardSearchRequest.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (aliasNames.length == 1) {
 AliasMetadata alias = aliases.get(aliasNames[0]);
 if (alias == null) {
 // This shouldn't happen unless alias disappeared after filteringAliases was called.
 throw new InvalidAliasNameException(index; aliasNames[0]; "Unknown alias name was passed to alias Filter");
 return parserFunction.apply(alias);
 } else {
 // we need to bench here a bit; to see maybe it makes sense to use OrFilter
 BoolQueryBuilder combined = new BoolQueryBuilder();


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content