-
Notifications
You must be signed in to change notification settings - Fork 56
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
"Connection pool is full, discarding connection" warning #49
Comments
As per requests documentation in the module requests.packages.urllib3.connectionpool:
I don't think this is a big problem, but we may need to increase the pool size, so that the connections are not discarded that often. |
I am receiving the folowing error:
Many times when trying to get a report for ~2000 domains. Has this connection pool issue been resolved? I get it if I send all 2000 at once or if I iterate over the domains making an API call per domain.
|
The reason for this issue was that the customized SSL Adapter mounted to each session was using a max HTTPConnectionPool size of 10. Specifically, this meant that each connection pool corresponding to a specific host could only issue 10 requests asynchronously per batch before filling up and discarding the connection. The fix was as simple as specifying for the adapter to take in a maximum pool size corresponding to the max of the |
Fixed with #74. |
This warning pops up sometimes when running the OSXCollector Analyze Filter:
Not sure if it means that a particular connection is dropped and the results are never gonna be obtained for a certain domain.
The text was updated successfully, but these errors were encountered: