Filter issue in higher environments

[MohitKumarK]

In higher environments (stage, prod) filter option is not working in sites.html.

Below error is observed in logs.

ET /mnt/overlay/granite/ui/content/shell/omnisearch/searchresults.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught SlingException
org.apache.jackrabbit.oak.query.RuntimeNodeTraversalException: The query read or traversed more than 100000 nodes. To avoid affecting other tasks, processing was stopped.
	at org.apache.jackrabbit.oak.query.FilterIterators.checkReadLimit(FilterIterators.java:70) [org.apache.jackrabbit.oak-core:1.22.3]

 Is there any other option apart of increasing -Doak.queryLimitInMemory=500000 -Doak.queryLimitReads=100000

Any help would be appreciated. 

[Sanket_Kumbharkhane · Accepted solution]

Hi @MohitKumarK,

As per the logs, it looks like a query does not resolve to an index or not optimize properly.

Visit the AEM Query Performance operations console and Explain slow queries looking for traversal or no index query explanations

You can try these 3 solutions:

1. Optimise your query so that the query resolves to an existing Lucene Property Index.

2. Adjust the query’s nodetype restriction so the query resolves to an existing Lucene Property Index.

3.  The query should resolve to a Lucene Property Index. If no index can be resolved, jump to Creating a new Index.

reference doc : https://experienceleague.adobe.com/docs/experience-manager-64/developing/bestpractices/troubleshooti...

[MohitKumarK]

Hi @Sanket_Kumbharkhane ,

There is an existing lucene index which the query is resolving to. but there are more number of nodes/pages to search.

[Jörg_Hoh]

Have you customized Omnisearch and written your own plugins? In that case you fire a query, which is not backed by an index and which traverses too much nodes, thus is very inefficient.

If you haven't customized Omnisearch, please reach out to Adobe support.