Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

AsyncSchemaRegistryClient is unable to handle concurrent requests

See original GitHub issue

Describe the bug

Related to https://github.com/encode/httpx/issues/1478, I’m getting this exception while using the same instance of AsyncSchemaRegistryClient in two different places, raising httpx.RemoteProtocolError: can't handle event type ConnectionClosed when role=SERVER and state=SEND_RESPONSE. The source code of the client is similar to the example that shows how to reproduce the issue in httpx and the answer to this comment mentions using the context manager once at a time would be the fix to it.

I could manage to overcome this issue by creating one instance of the client for every class that depends on AsyncSchemaRegistryClient

To Reproduce Steps to reproduce the behavior:

I’ll need some time to write a small snippet to reproduce it, so bear with me 😬

Expected behavior

The client is able to handle two (or more) concurrent calls to the schema registry

Issue Analytics

State:
Created 2 years ago
Comments:9 (7 by maintainers)

Top GitHub Comments

1reaction

thiromicommented, Feb 10, 2022

@marcosschroh I’ll try it and let you know 👍

0reactions

thiromicommented, Apr 11, 2022

@marcosschroh I’m using httpx==0.22.0

Top Results From Across the Web

Issues · marcosschroh/python-schema-registry-client - GitHub

marcosschroh / python-schema-registry-client Public ... AsyncSchemaRegistryClient is unable to handle concurrent requests.

Error while forwarding register schema request to the master

We cannot really tell when write requests start failing. ... AsyncHttpConnection.handle(AsyncHttpConnection.java:82) ... at scala.concurrent.forkjoin.

Async Python Schema Registry Client - Marcos Schroh

Client. The Schema Registry Client consumes the API exposed by the schema-registry to operate resources that are avro schemas.

confluent_kafka API — confluent-kafka 1.9.0 documentation

Multiple resources and resource types may be requested, but at most one resource of type ... The broker name/address this metadata originated from....

Troubleshooting Schema Registry - Cloudera Documentation

... do if you are not able to view Atlas metadata from Schema Registry? Mirroring schemas from Schema Registry to Atlas is done...