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

bug: resource usage #140

Open
erhant opened this issue Nov 5, 2024 · 4 comments
Open

bug: resource usage #140

erhant opened this issue Nov 5, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@erhant
Copy link
Member

erhant commented Nov 5, 2024

Problem

The process may sometimes reach ulimit and therefore give errors during API calls such as Os { code: 24, kind: Uncategorized, message: \"No file descriptors available\" })) } during a DNS lookup.

How to Reproduce

Not yet known.

Expected Behaviour

Should not give error.

Version

  • 0.2.18
@erhant erhant added the bug Something isn't working label Nov 5, 2024
@erhant
Copy link
Member Author

erhant commented Nov 5, 2024

hyperium/hyper#1422 related?

@erhant
Copy link
Member Author

erhant commented Nov 5, 2024

@erhant
Copy link
Member Author

erhant commented Nov 8, 2024

by using lsof -c <process-name-here> on the compute node, we have seen that as the peer count grows file descriptors are used more and more, eventually hitting the default limit of 1024.

on a separate note, the peer count is almost 1-1 correlated with the established outgoing connections count, so as a quick solution we have added a limiter on this count, effectively setting a cap on the number of all peers of a node.

@erhant
Copy link
Member Author

erhant commented Nov 19, 2024

setting the maximum established outgoing connections allows to set a cap on this resource usage

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant