-
Notifications
You must be signed in to change notification settings - Fork 27
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
Crash in grpc ("Too many open files") #10
Comments
Is the issue still relevant? |
Hi! I cannot test this on the latest version right now. We are currently using an old version (0.60.0) and the issue is still there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Posting here as recommended by YC support.
We use Ubuntu 18.04.3, python 3.6.9, yandexcloud 0.34.0, grpc 1.28.1.
Our application continuously starts and stops instances in YC, making no more than a few hundred API requests an hour (probably less). We ran into the problem that after running this way for some time (perhaps a couple of days) the application inevitably crashes with a stack trace like
Before the crash the grpc library also outputs error messages, e.g.:
This may be caused by a known problem in grpc. E.g. see grpc/grpc#15759 and related issues.
As a workaround, we tried setting nofile OS limit to a very high value. This results in the following behavior: over the course of several days (or weeks) average cpu load of the application grows (presumably caused by an ever-growing number of open files) until it hits 100% the app becomes completely unresponsive.
It should be noted that when using AWS EC2 SDK/cloud for instance management in an otherwise identical app under a very similar load, no issues of this kind occur. This is an indication that the problem is truly an issue in YC SDK.
The text was updated successfully, but these errors were encountered: