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

flower leaking memory #427

Open
jpopelka opened this issue Jan 3, 2023 · 5 comments
Open

flower leaking memory #427

jpopelka opened this issue Jan 3, 2023 · 5 comments

Comments

@jpopelka
Copy link
Member

jpopelka commented Jan 3, 2023

Screenshot from 2023-01-03 19-58-16

I don't remember this happening before. Perhaps, just try an older image and not the :latest.

This is unlikely to have the same cause as packit/packit-service#1824 because the flower image is not fedora based.

BTW: We should build our own image from the Dockerfile and push it to Quay.io (the same way we do with fluent-plugin-splunk-hec) to not use the image from Docker hub (I didn't notice we still do because there's no docker.io/ prefix.

@mfocko
Copy link
Member

mfocko commented Jan 3, 2023

at least from the start it looks rather periodic, I wouldn't be surprised if it's garbage collection…

@jpopelka
Copy link
Member Author

jpopelka commented Jan 4, 2023

OpenShift says OOMKilled

@jpopelka
Copy link
Member Author

jpopelka commented Jan 4, 2023

Perhaps, just try an older image and not the :latest

:latest is 5 months old so we should have seen this already in the past months

This is unlikely to have the same cause as packit/packit-service#1824 because the flower image is not fedora based.

although flower is run as a celery command so it somehow might have the same cause

@jpopelka
Copy link
Member Author

@lachmanfrantisek
Copy link
Member

@mfocko just checked it's still happening... (Looks related to the amount of Packit usage.)

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

No branches or pull requests

3 participants