We see lot of traversal warnings for queries which use index event.job.topic.
Not sure when exactly this query is triggered by AEM for page activation.
*WARN* [00.11.2.33 [678890-=] GET /content/domain/xx/yy/zz/page/child.pages.json HTTP/1.1] org.apache.jackrabbit.oak.plugins.index.property.strategy.ContentMirrorStoreStrategy Traversed 5000 nodes (259 index entries) using index event.job.topic with filter Filter(query=select [jcr:path], [jcr:score], * from [slingevent:Job] as a where [event.job.topic] = 'com/day/cq/replication/job/publish' and [slingevent:finishedState] is null order by [slingevent:created] /* xpath: //element(*,slingevent:Job)[@event.job.topic = 'com/day/cq/replication/job/publish' and not(@slingevent:finishedState)] order by @slingevent:created ascending */, path=*, property=[slingevent:finishedState=[is null], event.job.topic=[com/day/cq/replication/job/publish1]])
*WARN* [qtp1937001383-1061] org.apache.jackrabbit.oak.query.FilterIterators The query read more than 5000 nodes in memory.
java.lang.UnsupportedOperationException: The query read more than 5000 nodes in memory. To avoid running out of memory, processing was stopped.
at org.apache.jackrabbit.oak.query.FilterIterators.checkMemoryLimit(FilterIterators.java:46)
at org.apache.jackrabbit.oak.spi.query.Cursors$PathCursor$1.apply(Cursors.java:186)
at org.apache.jackrabbit.oak.spi.query.Cursors$PathCursor$1.apply(Cursors.java:180)
