Background of the issue : We are using Magnolia CMS with customized UI. As a first step of using Magnolia, we are migrating old content including documents to Magnolia. Content migration is working fine. Issue with DAM. We have more than 50 GB of historical content to be stored in Magnolia. Storing in DB became very expensive. We decided to save them in File system. Magnolia running in Kubernetes cluster as a service.
Problem: After we migrate dam from old system to magnolia, we are trying to publish asset from author to public instance. After MAx 200 documents published, It is killing the pod. In logs, we are not seeing anything. Last message is Catalish.sh killed...
Could you please suggest if anyone come across such scenarios. Best practices to implement dam and other configuration.
In Datadog, have seen that threadcounts are always more and GC is going crazy.
Thank you in advance.