Logs getting filled with Indexing warnings | Community
Skip to main content
ranadyutis95334
ranadyutis95334
Level 3
September 19, 2016

Logs getting filled with Indexing warnings

  • September 19, 2016
  • 5 replies
  • 6018 views

Hi,

In the log files I am getting the below warnings related to indexing. How to prevent it or what action is required?

 

19.09.2016 13:50:56.565 *WARN* [10.148.117.100 [1474291853171] GET /bin/security/authorizables.json HTTP/1.1] org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor Traversed 409000 nodes with filter Filter(query=select [jcr:path], [jcr:score], * from [nt:base] as a where [rep:principalName] is not null and isdescendantnode(a, '/home') /* xpath: /jcr:root/home//element(*)[@rep:principalName] */, path=/home//*, property=[rep:principalName=[is not null]]); consider creating an index or changing the query
19.09.2016 13:51:00.035 *WARN* [10.148.117.100 [1474291853171] GET /bin/security/authorizables.json HTTP/1.1] org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor Traversed 410000 nodes with filter Filter(query=select [jcr:path], [jcr:score], * from [nt:base] as a where [rep:principalName] is not null and isdescendantnode(a, '/home') /* xpath: /jcr:root/home//element(*)[@rep:principalName] */, path=/home//*, property=[rep:principalName=[is not null]]); consider creating an index or changing the query
19.09.2016 13:51:05.281 *WARN* [10.148.117.100 [1474291853171] GET /bin/security/authorizables.json HTTP/1.1] org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor Traversed 411000 nodes with filter Filter(query=select [jcr:path], [jcr:score], * from [nt:base] as a where [rep:principalName] is not null and isdescendantnode(a, '/home') /* xpath: /jcr:root/home//element(*)[@rep:principalName] */, path=/home//*, property=[rep:principalName=[is not null]]); consider creating an index or changing the query
19.09.2016 13:51:08.999 *WARN* [10.148.117.100 [1474291853171] GET /bin/security/authorizables.json HTTP/1.1] org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor Traversed 412000 nodes with filter Filter(query=select [jcr:path], [jcr:score], * from [nt:base] as a where [rep:principalName] is not null and isdescendantnode(a, '/home') /* xpath: /jcr:root/home//element(*)[@rep:principalName] */, path=/home//*, property=[rep:principalName=[is not null]]); consider creating an index or changing the query

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

5 replies

smacdonald2008
smacdonald2008
Level 10
September 19, 2016

Looks like Indexing is not configured properly. Watch this GEMS session on Indexing: 

https://docs.adobe.com/ddc/en/gems/oak-lucene-indexes.html

Hope this helps... 

Feike_Visser1
Adobe Employee
Feike_Visser1Adobe Employee
Adobe Employee
September 19, 2016

What version of AEM is this?

ranadyutis95334
ranadyutis95334Author
Level 3
September 19, 2016

6.1

smacdonald2008
smacdonald2008
Level 10
September 19, 2016

Did you configure Indexing as explained in the GEMs session that i referened?

V
Adobe Employee
vmehrotrAdobe Employee
Adobe Employee
September 19, 2016

Disable the ootb property index 'authorizables' by changing type to disabled.

Apply the lucene based index.

<authorizables jcr:primaryType="oak:QueryIndexDefinition" async="async" compatVersion="{Long}2" name="authorizables" reindex="{Boolean}true" indexPath="/oak:index/authorizables" excludedPaths="[/var,/etc/replication,/etc/workflow/instances,/jcr:system]" type="lucene"> <aggregates jcr:primaryType="nt:unstructured"> <rep:Authorizable jcr:primaryType="nt:unstructured"> <include0 jcr:primaryType="nt:unstructured" path="profile" relativeNode="{Boolean}false"/> </rep:Authorizable> </aggregates> <indexRules jcr:primaryType="nt:unstructured"> <rep:Authorizable jcr:primaryType="nt:unstructured"> <properties jcr:primaryType="nt:unstructured"> <repPrincipalName jcr:primaryType="nt:unstructured" analyzed="{Boolean}true" name="rep:principalName" ordered="{Boolean}true" propertyIndex="{Boolean}true" type="String"/> <repAuthorizableId jcr:primaryType="nt:unstructured" analyzed="{Boolean}true" name="rep:authorizableId" ordered="{Boolean}true" propertyIndex="{Boolean}true" type="String"/> <profileEmail jcr:primaryType="nt:unstructured" analyzed="{Boolean}true" name="profile/email" ordered="{Boolean}false" propertyIndex="{Boolean}true" type="String"/> <profileGivenName jcr:primaryType="nt:unstructured" analyzed="{Boolean}true" name="profile/givenName" ordered="{Boolean}false" propertyIndex="{Boolean}true" type="String"/> <profileFamilyName jcr:primaryType="nt:unstructured" analyzed="{Boolean}true" name="profile/familyName" ordered="{Boolean}false" propertyIndex="{Boolean}true" type="String"/> <profileGender jcr:primaryType="nt:unstructured" analyzed="{Boolean}true" name="profile/gender" ordered="{Boolean}false" propertyIndex="{Boolean}true" type="String"/> </properties> </rep:Authorizable> </indexRules> </authorizables>
M
mmohta11
Level 2
June 19, 2017

Hi All,

We facing same issue in AEM 6.1.

Is this resolved issue by creating index.

vmehrotr​ the query mentioned is on nt:base and index is on rep:Authorizable will this be picked up by the query engine or do we need to create index on nt:base.

somasreeb857955
somasreeb857955
August 2, 2019

Looks like we had the same query traversal on our 6.2 AEM few days earlier,

30.07.2019 15:36:32.032 *WARN* [130.208.54.25 [1564500088801] GET /bin/security/authorizables.json HTTP/1.1] org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor Traversed 2035000 nodes with filter Filter(query=select [jcr:path], [jcr:score], * from [nt:base] as a where [rep:principalName] is not null and isdescendantnode(a, '/home') /* xpath: /jcr:root/home//element(*)[@rep:principalName] */, path=/home//*, property=[rep:principalName=[is not null]]); consider creating an index or changing the query

Is there any particular source for such queries like being system generated, or been particularly when run by someone against the home path?

Terms & ConditionsAccessibility statement

Loading footer...