AEM Version "Preview" feature on parent folders, leads to Index Updates and performance impact.

[Raks1990]

We have observed a problem, where everytime a user tries a "Preview" action from Timeline on a parent page, example /content/we-retail page for any version number, it causes index traversals like below:

POST /mnt/overlay/wcm/core/content/sites/versionhistory/_jcr_content.txt HTTP/1.1] org.apache.jackrabbit.oak.plugins.index.IndexUpdate Incremental indexing Traversed #10000

While this is seen for other operations too in AEM with heavy structure, but for Preview only, the index updates for existing oak:indexes (OOTB and custom) also get triggered, and can cause AEM slowness.

org.apache.jackrabbit.oak.plugins.index.IndexUpdate /oak:index/lucene => Indexed 10000 nodes in 753.8 ms

The time window for these logs varies based on the content size, but is replicable in vanilla for we-retail as well.

No other AEM functionality for sites, seen to cause logs like : org.apache.jackrabbit.oak.plugins.index.IndexUpdate /oak:index/lucene => Indexed 10000 nodes in 753.8 ms

Only traversals happen usually.

Any suggestions why a version preview (not compare/restore) needs to trigger a Index update for all oak:indexes, and how to eliminate the oak:index updates to get triggered? Can this be considered a product bug?

AEM version in use: 6.5.18

Oak version in use: Apache Jackrabbit Oak 1.22.18

Thanks in Advance.

[EstebanBustamante · Accepted solution]

Hi, 

Please try to reproduce the issue using the WKND site because the We.Retail project is deprecated. If you can reproduce it, then submit a support ticket to Adobe; it's likely a bug.