Pod spin time is too much

Experience Manager (PaaS/OnPrem)
1

Hi team,

We are running Bloomreach Experience Manager (brXM 14.5.0) across multiple environments (GKE and AWS). Currently, whenever the CMS pod is restarted or redeployed, the application takes 20–30+ minutes to become available. This long startup time significantly impacts development velocity, deployment cycles, and operational stability.

What are the common causes for slow pod startup in BRXM 14.5.0, and what configuration changes, optimizations can help speed up pod startup time?

2

Hello, is it rebuilding the index every time? Lucene Index Export add-on - Bloomreach Experience Manager (PaaS/Self-Hosted) - The Fast and Flexible Headless CMS