-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Event stream api leaks file handles #8864
Labels
In Progress
This issue is actively being worked by the assignee, please do not work on this at this time.
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
openshift-ci-robot
added
the
kind/bug
Categorizes issue or PR as related to a bug.
label
Jan 2, 2021
What |
It's a standard fedora setup with journald backend.
|
nice report ... i assume we are talking about these ...
|
baude
added
the
In Progress
This issue is actively being worked by the assignee, please do not work on this at this time.
label
Jan 4, 2021
@baude yes, lots of journal descriptors. Thx for having a look! 🧯 |
baude
added a commit
to baude/podman
that referenced
this issue
Jan 4, 2021
when reading from journald, we need to close the journal handler for events and logging. Fixes: containers#8864 Signed-off-by: baude <[email protected]>
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 22, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
In Progress
This issue is actively being worked by the assignee, please do not work on this at this time.
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Repetitiv event stream API requests leak file handles.
Steps to reproduce the issue:
curl -s --unix-socket /run/podman/podman.sock http://localhost/v1/libpod/containers/stats
watch "lsof -p $(pgrep -f 'podman.*system service') | wc -l"
curl -m 1 -s --unix-socket /run/podman/podman.sock http://localhost/v1/libpod/events
Describe the results you received:
Number of file handles is growing with each subsequent "events" subscription until the podman system service is restarted.
The problem can be monitored on a idle system without starting/stopping containers.
Additional information you deem important (e.g. issue happens only occasionally):
I found this while working on the nomad podman driver. We try to leverage event and stats streams to improve the performance.
Running our unit tests exhausted the open file limit and i started to hunt the problem.
Output of
podman version
:The text was updated successfully, but these errors were encountered: