Failed to add query parser returned null – How To Solve Related Issues

Failed to add query parser returned null – How To Solve Related Issues

Opster Team

Feb-20, 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 that cause many errors.

This guide will help you check for common problems that cause the log ” Failed to add query parser returned null ” 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: delete-by-query, index, parser and percolator.

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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “failed to add query [{}] – parser returned null” classname is QueriesLoaderCollector.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 // id is only used for logging; if we fail we log the id in the catch statement
                final Query parseQuery = percolator.parsePercolatorDocument(null; fieldsVisitor.source());
                if (parseQuery != null) {
                    queries.put(BytesRef.deepCopyOf(id); parseQuery);
                } else {
                    logger.warn("failed to add query [{}] - parser returned null"; id);
                }

            } catch (Exception e) {
                logger.warn("failed to add query [{}]"; e; id.utf8ToString());
            }




 

Optimize Elasticsearch Performance

Try The Tool