- Publish requests are queueing up in the replication agent queue
- Published contents are not showing up on the publish server
- Impact on system performance
What causes Replication issues:
- Replication agent is misconfigured and cannot connect to the publish agent
- There is an error at the time of replication causing the replication queue to get stuck
- The system is slow and replications are getting processed slowly
- The replication is happening as part of custom workflow and the problem is with workflow processing.
How to analyze Replication issues:
1. Check the replication queue status:
Active: when items are being processed.
Idle: when the queue is empty.
Blocked: when items are in the queue, but cannot be processed; for example, when the agent points to a host that is down or non-existent.
2. Review the replication configurations if your server is cloned or the agent has been configured recently. For details, see here.
3. Review the replication agent logs at http://localhost:4502/etc/replication/agents.author/AgentName.log.html#end. If you can’t identify any items collect this log and present it to AEM support.
4. Review the server error.log from AEMinstall/crx-quickstart/logs; If you can’t identify any items collect this log and present to AEM support.
5. If the replication queue is in an “idle” state and none of the above applies, in this case, the problem is most likely caused by the workflows. If the workflows are not being processed then the replication item never gets to the replication queue. To monitor the status of your workflows, you can check the workflow dashboard to check the number of running workflow instances. You can read about administering workflows here.
6. Replications slows down when the system is under high load or experience other performance issues.
1. Check the replication queue status:
Active: when items are being processed.
Idle: when the queue is empty.
Blocked: when items are in the queue, but cannot be processed; for example, when the agent points to a host that is down or non-existent.
2. Review the replication configurations if your server is cloned or the agent has been configured recently. For details, see here.
3. Review the replication agent logs at http://localhost:4502/etc/replication/agents.author/AgentName.log.html#end. If you can’t identify any items collect this log and present it to AEM support.
4. Review the server error.log from AEMinstall/crx-quickstart/logs; If you can’t identify any items collect this log and present to AEM support.
5. If the replication queue is in an “idle” state and none of the above applies, in this case, the problem is most likely caused by the workflows. If the workflows are not being processed then the replication item never gets to the replication queue. To monitor the status of your workflows, you can check the workflow dashboard to check the number of running workflow instances. You can read about administering workflows here.
6. Replications slows down when the system is under high load or experience other performance issues.
Solution to Common Replication issues:
1) Review the Replication queue issues
2) If the problem is due to the workflows not running efficiently, you may review the concurrent workflow processing tips
3) For issues related to the overall AEM slow performance and replication, you may review AEM Performance Issues
1) Review the Replication queue issues
2) If the problem is due to the workflows not running efficiently, you may review the concurrent workflow processing tips
3) For issues related to the overall AEM slow performance and replication, you may review AEM Performance Issues
No comments:
Post a Comment
If you have any doubts or questions, please let us know.