Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Help needed on Index Query

Avatar

Avatar
Validate 1
Level 1
nitins96420484
Level 1

Likes

3 likes

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile

Avatar
Validate 1
Level 1
nitins96420484
Level 1

Likes

3 likes

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
nitins96420484
Level 1

13-05-2020

Hi Experts,

 

Our Log shows this error and we need to add Index to our repository for the same.

I am not sure though what the Index should be fo rofllowing query, Please help:

 

On Prod Author1 - Occurrence of Errors/Warnings:  consider creating an index or changing the query.

 

Reason : Missing search index that causes large repository traversal causing performance issues due to high disk I/O.

 

Recommended Actions: Contact customizer to create required search index .

 

Example from logs :

11.05.2020 12:18:25.885 *WARN* [Thread-95] org.apache.jackrabbit.oak.plugins.index.Cursors$TraversingCursor Traversed 1000 nodes with filter Filter(query=select e.[jcr:path] as [jcr:path], e.[jcr:score] as [jcr:score], e.* from [nt:base] as a inner join [nt:base] as b on ischildnode(b, a) inner join [nt:base] as c on ischildnode(c, b) inner join [nt:base] as d on ischildnode(d, c) inner join [nt:base] as e on ischildnode(e, d) where name(a) = 'wcm' and isdescendantnode(a, '/home') and name(b) = 'notification' and name(c) = 'config' and name(d) = 'subscriptions' and e.[type] = 'page' option(traversal OK) /* xpath: /jcr:root/home//wcm/notification/config/subscriptions/* [@type='page'] option(traversal ok) */, path=/home//*, property=[:localname=[wcm]]); consider creating an index or changing the query

index

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Springboard
MVP
Shashi_Mulugu
MVP

Likes

232 likes

Total Posts

294 posts

Correct Reply

67 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Applaud 100
Establish
View profile

Avatar
Springboard
MVP
Shashi_Mulugu
MVP

Likes

232 likes

Total Posts

294 posts

Correct Reply

67 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Applaud 100
Establish
View profile
Shashi_Mulugu
MVP

13-05-2020

Looks like a bug in ACS commons inbox feature. Workaround is
Stop the component in /system/console/components ->notification: com.day.cq.wcm.notification.impl.NotificationManagerImpl and to keep it stopped by using ACS-commons component disabler
https://adobe-consulting-services.github.io/acs-aem-commons/features/osgi-disablers/component-disabl...

 

Refer: https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/1635

Answers (2)

Answers (2)

Avatar

Avatar
Establish
MVP
Veena_Vikram
MVP

Likes

484 likes

Total Posts

1,048 posts

Correct Reply

121 solutions
Top badges earned
Establish
Coach
Contributor 2
Seeker
Ignite 5
View profile

Avatar
Establish
MVP
Veena_Vikram
MVP

Likes

484 likes

Total Posts

1,048 posts

Correct Reply

121 solutions
Top badges earned
Establish
Coach
Contributor 2
Seeker
Ignite 5
View profile
Veena_Vikram
MVP

13-05-2020

Are you searching for a property called "wcm" ? 

Avatar

Avatar
Level 1
Sabarishreddy
Level 1

Likes

0 likes

Total Posts

5 posts

Correct Reply

0 solutions
View profile

Avatar
Level 1
Sabarishreddy
Level 1

Likes

0 likes

Total Posts

5 posts

Correct Reply

0 solutions
View profile
Sabarishreddy
Level 1

28-04-2021

This is still occurring and the accepted solution wasn't the root cause. Can anyone in AEM take a look at this issue? looks like the wcm core aem component is generating the query and can help fixing this issue.