thanks for the quick reply. is there any way for me to disable it, or at least reduce the amount of memory it consumes? or for a change reduce the data capacity that being loaded from the wal?
thanks in advance. On Tuesday, 2 February 2021 at 16:25:06 UTC+2 [email protected] wrote: > You will need to give the instance more memory in order to complete the > recovery. > > On Tue, Feb 2, 2021 at 2:32 PM hamisa <[email protected]> wrote: > >> 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 >> >> <https://groups.google.com/d/msgid/prometheus-users/b967175e-9658-4d6e-ac27-bb62a5a2f70bn%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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/95931435-aab7-4859-94b1-aee7743841bfn%40googlegroups.com.
