You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it perhaps related to #13939, so if the Prometheus OOMs you have to delete the WAL (and reduce your scrape load) OR change memory limits if you want to recover from the OOM.
What did you do?
The node of prometheus work for scrape jobs on docker.
It down and restart fail for serval times, until clear wal.
What did you expect to see?
How to fix it, or correct the configuration.
What did you see instead? Under which circumstances?
Seem to write wal fail (the size of lastest 0000x file is zero) when out of memory, and then restart fail by reading the wal.
Note: sometime it logs "Error on ingesting out-of-order samples", but these sample had been droped.
System information
Linux 3.10.0-327.el7.x86_64 x86_64
Prometheus version
Prometheus configuration file
Alertmanager version
No response
Alertmanager configuration file
No response
Logs
The text was updated successfully, but these errors were encountered: