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

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

Updated: Feb-20

Elasticsearch Version: 1.7-8.0


To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 

To troubleshoot log “Failed to add query parser returned null” it’s important to understand a few problems related to Elasticsearch concepts delete-by-query, index, parser, percolator. See bellow important tips and explanations on these concepts

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());

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 Github Issue Number 33095  

Painless Scripting Compile Errors  


About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now