Hi there, I'm running prometheus 2.17 on my openshift 3.9.43 cluster. when the prometheus pod collapse (deleted, evicted ...) the newly created pod start reading the wal segments in addiotion to run prometheus again. in that process the prometheus' pod container get into OOM state, and recreated just afterwards which causes CrashLoopBack to the pod.
is there any solution to this problem? thanks in advance. -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/b967175e-9658-4d6e-ac27-bb62a5a2f70bn%40googlegroups.com.
