We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
container_ooms
Hello!
We are observing what looks like a flood of container_ooms on many containers, which on inspection, mostly appear without restarts / OOMs.
This seems to be caused by a single container receiving an OOM which triggers an eviction
OOM
eviction_manager.go:367] "Eviction manager: pods ranked for eviction[...list of pods...]"
which is associated with many logs of
containerd[1320]: "TaskOOM event &TaskOOM{ContainerID:dd7ba888c8eb849fbffeb5da01bb8cf1034264757d3dff5d7d7815d4c4671200,XXX_unrecognized:[],}" ...
Guessing this could be related to containerd/containerd#7102
From https://pkg.go.dev/github.com/containerd/containerd/api/events?utm_source=godoc#TaskOOM it doesn't look like there's a way to distinguish between false and true TaskOOM eventss.
TaskOOM
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello!
We are observing what looks like a flood of
container_ooms
on many containers, which on inspection, mostly appear without restarts / OOMs.This seems to be caused by a single container receiving an
OOM
which triggers an evictionwhich is associated with many logs of
Guessing this could be related to containerd/containerd#7102
From https://pkg.go.dev/github.com/containerd/containerd/api/events?utm_source=godoc#TaskOOM it doesn't look like there's a way to distinguish between false and true
TaskOOM
eventss.The text was updated successfully, but these errors were encountered: