Cette conversation a été verrouillée en raison de son inactivité. Veuillez créer une nouvelle publication.
Niveau 1
Niveau 2
Se connecter à la communauté
Connectez-vous pour voir tous les badges
Cette conversation a été verrouillée en raison de son inactivité. Veuillez créer une nouvelle publication.
Hi Team,
Production author outage happened two days ago. We can see update_asset transaction took more time around 169 sec also the most time consuming 50.8%. We have noticed that around 50 assets were uploaded on that day. We are not able to identify the root cause for this outage. In order to prevent these outages in the future what precautions we need to take. It is an AEM assets application.
Résolu ! Accéder à la solution.
Vues
Réponses
Nombre de J’aime
Here are some of the Assets best practices you might want to implement: Best Practices for Assets
Scrape through logs for more information, probably Update asset workflow or xmp writeback could be the reason.
You may go through Assets Performance Tuning Guide for pointers
Vues
Réponses
Nombre de J’aime
Here are some of the Assets best practices you might want to implement: Best Practices for Assets
50 assets should not cause an outage. There is probably something else that caused the outage. Analyze the following information:
- Log files
- Thread Dumps[1]
- Heap Dumps [2]
If you are not able to find anything, I would recommend logging a daycare ticket.
Vues
Réponses
Nombre de J’aime
Take the thread dumps (at least 5) as suggested during the time the issue happens and run analysis on it using thread dump analyzers available [1].
Vues
Réponses
Nombre de J’aime
Vues
Likes
Réponses