Adobe Debugging Server

 

http://localhost:4502/etc/reports/diskusage.html?path=/content

http://localhost:4502/etc/versioning/purge.html

/libs/granite/operations/content/diagnosistools/queryPerformance.html

SELECT * FROM [nt:base] WHERE ISDESCENDANTNODE([/content]) AND [cq:master] IS NOT NULL

Check index faliling or not

http://localhost:4502/system/console/jmx/org.apache.jackrabbit.oak%3Aname%3Dasync%2Ctype%3DIndexStats

http://localhost:4502/system/console/jmx/org.apache.jackrabbit.oak%3Aname%3Dasync-reindex%2Ctype%3DIndexStats

http://localhost:4502/system/console/jmx/org.apache.jackrabbit.oak%3Aname%3Dfulltext-async%2Ctype%3DIndexStats

/libs/granite/operations/content/diagnosistools/indexManager.html

The volumes are "cold" when you first restore them and take a while to warm

One thing i used to was run "chown -R crx:crx /mnt"

to touch each file and speed up the warming process

Methodical and Staged approach: 

1. Go to http://localhost:4502/etc/reports/diskusage.html?path=/content and this will highlight the node size and the amount of space used by the nodes.
2. Navigate deeper and find which path has the most of number of nodes.
3. Select a brand/path and make a note of the nodes currently being used.
4. Manually purge the brand/path in 3 through http://localhost:4502/etc/versioning/purge.html. We recommend undertaking a Dry Run before committing the Purge.
5. Check the logs for any errors related to the version purge [1]
6. Review http://localhost:4502/etc/reports/diskusage.html?path=/content and validate the nodes have been reduced.
7. If successful add the version purge into http://localhost:4502/system/console/configMgr/com.day.cq.wcm.core.impl.VersionPurgeTask for the brand/path in 3. 
8. Repeat 1-7 for different brands/paths 
9. This exercise will increase the index size, but this is normal. You will need to run an Offline compaction to have the size reduced.

 

Note: Please replace all references to http://localhost:4502 with those relevant to the Unilever environment.

 

[1] Please ensure any external logging tools are highlighting any references to ‘com.day.cq.wcm.core.impl.VersionManagerImpl’