Symptoms of indexing issues
The following are signs of an issue with AEM/Oak indexing:
- Search results are outdated by more than 10 minutes
- There are missing search results
- Errors are returned either in the UI or logs during search via site UI, Query Builder search, or JCR query execution
Diagnosing an indexing issue
- To see if asynchronous indexing is slow or failing, do the following:
1. Open these URLs on your AEM instance to view stats about the Async indexer
http://aemhost:port/system/console/jmx/org.apache.jackrabbit.oak%3Aname%3Dasync%2Ctype%3DIndexStats
http://aemhost:port/system/console/jmx/org.apache.jackrabbit.oak%3Aname%3Dfulltext-async%2Ctype%3DIndexStats - This URL only applies to AEM6.2 and later
2. On each of those pages, check these fields:
FailingSince - This indicates when indexing first started failing.
LastError - This is the stack trace showing what is causing indexing to fail. If this is empty then indexing isn't failing.
LastErrorTime - This indicates the last time indexing threw the error.
LastIndexedTime - If the date and time of this field is over 5 minutes old then indexing is running too slow.
What causes issues with indexing
- Improper maintenance or failure to perform maintenance such as Revision Garbage Collection, Workflow Purge, Audit Purge, Version Purge, etc.
- Corrupt or missing segments in Tar storage
- Revision Corruption in a clustered environment (DocumentNodeStore - Mongo or Database)
- An issue with the cluster topology in a clustered environment
How to analyze what is causing indexing issues
- See this article for analyzing and fixing indexing issues
No comments:
Post a Comment