You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using libraries which use urllib3 in multiple threads, an end-user often sees the warning log:
urllib3.connectionpool: Connection pool is full, discarding connection: cloud.example.com. Connection pool size: 42
The warning only really needs to be displayed once (per pool), and future logs could probably be debug-level. Reducing the verbosity of logging will make it more informative and less likely to be ignored.
Alternatives
It's possible to go through each SDK's method of increasing the connection pool size to the thread count (if that configuration is exposed) to remove the warning, but this isn't the real issue here.
I just wanted to toss my hat into the ring and say that this is for sure something my team would utilize. Honestly, I'd prefer the option to disable the warning entirely.
I've tried to disable the warning with:
import warnings
with warnings.catch_warnings(action="ignore"):
Context
When using libraries which use urllib3 in multiple threads, an end-user often sees the warning log:
The warning only really needs to be displayed once (per pool), and future logs could probably be debug-level. Reducing the verbosity of logging will make it more informative and less likely to be ignored.
Alternatives
It's possible to go through each SDK's method of increasing the connection pool size to the thread count (if that configuration is exposed) to remove the warning, but this isn't the real issue here.
Duplicate
Related: #3074
Contribution
I would be happy to submit a PR
The text was updated successfully, but these errors were encountered: