The query read or traversed more than 100000 nodes. To avoid affecting other tasks, processing was stopped - AEM extracts

Avatar

Avatar
Validate 10
Level 3
tc82
Level 3

Likes

21 likes

Total Posts

64 posts

Correct reply

0 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Validate 10
Level 3
tc82
Level 3

Likes

21 likes

Total Posts

64 posts

Correct reply

0 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile
tc82
Level 3

24-03-2020

Am using  query builder.json to get the content details. While hitting the content node(/content/XX) am getting the exception:

The query read or traversed more than 100000 nodes. To avoid affecting other tasks, processing was stopped

 

 

I need all the data. May I know how can i achieve it?

Replies

Avatar

Avatar
Coach
Employee
jbrar
Employee

Likes

389 likes

Total Posts

869 posts

Correct reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile

Avatar
Coach
Employee
jbrar
Employee

Likes

389 likes

Total Posts

869 posts

Correct reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile
jbrar
Employee

24-03-2020

Either you can create the index for the query using the oakutils tool or update the traversal limit from [2]

 

NOTE: Increasing the traversal limit might lead to high memory usage.

 

[1] http://oakutils.appspot.com/generate/index

 

[2] http://<host>:<port>/system/console/jmx/org.apache.jackrabbit.oak%3Aname%3Dsettings%2Ctype%3DQueryEn...

Avatar

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,134 likes

Total Posts

3,161 posts

Correct reply

1,079 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,134 likes

Total Posts

3,161 posts

Correct reply

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

30-03-2020

This means that you have created a query which is not covered by any index, and which is thus aborted. You should create an index to match your query (or you should change your query to make use of an existing index).

What's your query, and what AEM version are you using?

Avatar

Avatar
Validate 10
Level 3
tc82
Level 3

Likes

21 likes

Total Posts

64 posts

Correct reply

0 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Validate 10
Level 3
tc82
Level 3

Likes

21 likes

Total Posts

64 posts

Correct reply

0 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile
tc82
Level 3

05-05-2020

Thank you all for the help. Am using aem 6.3 and we are using the query to generate the aem extracts. We were using the query builder.json. Currently purged the content and looking for long term plan, but now we are good.