Open snazzyfox opened 4 years ago
Any update on this? It is still an issue for us at @Simplebet and probably others
We are looking into this issue.
It looks like there's a PR submitted, can we get someone from the team to take a look? cc: @jliunyu
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)