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.

Sign up for GitHub

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

Jump to bottom

Handle Too Many Open Files (Open Connections) #6

Closed
JohannesEbke opened this issue Jan 8, 2019 · 1 comment
Closed

Handle Too Many Open Files (Open Connections) #6

JohannesEbke opened this issue Jan 8, 2019 · 1 comment
Labels
enhancement

Comments

@JohannesEbke
Copy link
Owner

If run with a nlimit of 1024, aws-list-all runs into OSErrors due to too many open files (connections).
@gliptak gliptak mentioned this issue Mar 5, 2019
Closed
@JohannesEbke JohannesEbke changed the title Handle Too Many Open Files Handle Too Many Open Files (Open Connections) Apr 14, 2019
@JohannesEbke
Copy link
Owner Author

The reason for this is that AWS has over 1000 endpoints (region/service pairs), and aws-list-all distributes requests randomly across these endpoints to avoid throttling.

Workaround: If you list regions one-by-one, you should not run out of open files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JohannesEbke