Unable to find filter ” + resourceId +” – Elasticsearch Error How To Solve Related Issues

Unable to find filter ” + resourceId +” – 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 “Unable to find filter ” + resourceId +”” 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: filter, plugin.

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”Unable to find filter [” + resourceId +”]”classname  is TransportGetFiltersAction.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

return MlFilter.LENIENT_PARSER.parse(parser; null).build();
  protected ResourceNotFoundException notFoundException(String resourceId) {
  return new ResourceNotFoundException("Unable to find filter [" + resourceId +"]");
  protected String executionOrigin() {
  return ML_ORIGIN;


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 android.content.res.Resources$NotFoundException: Unable to find resource ID #0xffffffff -views 49,217 ,score 67

Elasticsearch 'failed to find filter under name ' -views   3,258,score 1



About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now