3727635 - Solr pods restarting with OOMKilled during replication due to insufficient container memory

One or more Solr replica pods restart unexpectedly with OOMKilled status.

The following behavior may be observed:

• Only the leader node (for example: solr-0) remains stable.
• Replica nodes (for example: solr-1, solr-2, solr-3) restart repeatedly.
• High container memory utilization is observed on Solr pods.
• The issue occurs during or shortly after Solr collection replication.
• Kubernetes events or pod status indicate OOMKilled.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental." 

SAP Commerce Cloud

Solr, OOMKilled, Solr pods restart, Solr replication, Solr leader node, Solr replica node, Solr memory usage, JVM scale factor, container memory limit, Kubernetes OOMKilled, Solr cluster, SAP Commerce Cloud, Solr pod restart, high memory usage , KBA , CEC-SCC-COM-SRC-SER , Search and Navigation , Problem