Skip to content
New issue

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

OOM kill on do k8s #420

Closed
domino14 opened this issue Oct 30, 2023 · 1 comment
Closed

OOM kill on do k8s #420

domino14 opened this issue Oct 30, 2023 · 1 comment

Comments

@domino14
Copy link
Owner

this is happening like once a day:

[2023-10-30 02:03:04 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:1902781)
[2023-10-30 02:03:05 +0000] [1] [WARNING] Worker with pid 1902781 was terminated due to signal 9
[2023-10-30 02:03:05 +0000] [1960150] [INFO] Booting worker with pid: 1960150
[2023-10-30 02:03:06 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:1902782)
[2023-10-30 02:03:07 +0000] [1] [WARNING] Worker with pid 1902782 was terminated due to signal 9
[2023-10-30 02:03:07 +0000] [1960156] [INFO] Booting worker with pid: 1960156
@domino14
Copy link
Owner Author

I think k8s is running more crap on our cluster which is small already. We could also have a mem leak. But DO makes it difficult to see how much memory we're even using. Fargate would show this better (see #419)

Doubled memory of cluster which is more expensive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant