Filter issue in higher environments

Avatar

Avatar
Validate 1
Level 1
MohitKumarK
Level 1

Likes

3 likes

Total Posts

6 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 1
MohitKumarK
Level 1

Likes

3 likes

Total Posts

6 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
MohitKumarK
Level 1

16-02-2021

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. 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Give Back
Level 4
Sanket_Kumbharkhane
Level 4

Likes

46 likes

Total Posts

50 posts

Correct reply

20 solutions
Top badges earned
Give Back
Boost 5
Boost 3
Boost 25
Boost 10
View profile

Avatar
Give Back
Level 4
Sanket_Kumbharkhane
Level 4

Likes

46 likes

Total Posts

50 posts

Correct reply

20 solutions
Top badges earned
Give Back
Boost 5
Boost 3
Boost 25
Boost 10
View profile
Sanket_Kumbharkhane
Level 4

16-02-2021

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...

 

 

Answers (2)

Answers (2)

Avatar

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,135 likes

Total Posts

3,167 posts

Correct reply

1,080 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,135 likes

Total Posts

3,167 posts

Correct reply

1,080 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
Employee

20-02-2021

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. 

Avatar

Avatar
Validate 1
Level 1
MohitKumarK
Level 1

Likes

3 likes

Total Posts

6 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 1
MohitKumarK
Level 1

Likes

3 likes

Total Posts

6 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
MohitKumarK
Level 1

16-02-2021

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.