org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler Failed to create checkpoint

[Sai_duthGa]

Hi, 

    We have started seeing this recently where when we create a content fragment under a specific path it starts index update with below pattern and keeps on looping and does not stop. At the end of each loop it is showing following error: 

[sling-oak-1-org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate-async] org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler Failed to create checkpoint 869e77b7-7028-42b4-ade5-87fbb168a204 in 10 seconds

Index update log that is looping: It is looping till 70000 and starting again from 10000

GET /editor.html/content/dam/digital/test/fragments/dir1/en-us/places/hotel-florida HTTP/1.1] org.apache.jackrabbit.oak.plugins.index.IndexUpdate /oak:index/uuid => Indexed 10000 nodes in 3.219 s ..

 In the above hotel-florida is the content fragment. We were unable to identify the root cause or solution to fix this issue. We need to kill the java process to restart the application. Once the application is up everything works well and we don't see any index update until any of the content fragments in the specific path where the issue occurred is opened/created. Could someone help on this.

We are using AEM 6.5.7

Thanks.

[Raja_Reddy]

Hi @Sai_duthGa 

The issue you are experiencing with the continuous looping of index updates and the error message related to creating a checkpoint could be caused by a few different factors. Here are a few suggestions to help troubleshoot and resolve the issue:

1. Check for any custom code or workflows that might be triggering the index updates. Review any custom code or workflows that are executed when a content fragment is created or modified. Ensure that there are no infinite loops or recursive calls that could be causing the continuous index updates.

2. Verify the configuration of the Oak index. Check the configuration of the Oak index used for content fragments. Ensure that the index is properly configured and optimized for your specific use case. You can review the index configuration in the CRXDE Lite or by inspecting the repository.xml file.

3. Monitor the system resources. Check the system resources (CPU, memory, disk space) during the index update process. Ensure that the system has enough resources available to handle the indexing workload. If the system resources are constrained, it could lead to performance issues and the failure to create checkpoints.

4. Review the logs for any related errors or warnings. Check the AEM logs for any related errors or warnings that could provide more information about the issue. Look for any specific error messages or stack traces that could help identify the root cause of the problem.

5. Consider upgrading to the latest version of AEM. If you are using AEM 6.5.7, consider upgrading to the latest version of AEM 6.5.x. There might be bug fixes or improvements related to content fragments and indexing in the newer versions.

[Sai_duthGa]

@Raja_Reddy  We validated all the points above. Still the issue is happening. One thing to note is this index update or checkpoint creation failure is happening only for a specific path. Is there any other suggestion that could help?