-
Notifications
You must be signed in to change notification settings - Fork 880
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
Timeout Option for SchemaRegistryClient #905
Labels
Comments
Any update on this? It is still an issue for us at @simplebet and probably others |
We are looking into this issue. |
Duplicate of #622 |
It looks like there's a PR submitted, can we get someone from the team to take a look? cc: @jliunyu |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
SchemaRegistryClient does not supply a timeout to the underlying calls to
requests
. If a network issue causes no data to be returned (such as firewall/security group misconfiguration), the client will wait forever instead of raising a timeout error. This essentially causes the application to hang.We should add a new configuration option to SchemaRegistryClient that sets the timeout so that an error may be raised/caught in these situations.
How to reproduce
With a blackhole server running locally, for example on port 8000
Checklist
Please provide the following information:
confluent_kafka.version()
andconfluent_kafka.libversion()
): both 1.4.2{...}
: irrelevant'debug': '..'
as necessary)The text was updated successfully, but these errors were encountered: