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
Currently we use threads to operate all the subscriptions (listeners). While this is ok, we could take advantage of the event-based API from librdkafka to be able to do almost the same from a single thread. We would have to however ensure that:
None of listeners leak into the managing loop
They can be managed as they are
Their event bus operates independently (as it does now) for events publication
They are blocked only in their respective SG when processing
The text was updated successfully, but these errors were encountered:
Every single waiting flow could yield from a fiber to the managing thread.
mensfeld
changed the title
Provide single threaded multiplexing of connections and consumer group operations
Provide single threaded multiplexing of connections and subscription groups operations
Jan 18, 2024
Currently we use threads to operate all the subscriptions (listeners). While this is ok, we could take advantage of the event-based API from librdkafka to be able to do almost the same from a single thread. We would have to however ensure that:
The text was updated successfully, but these errors were encountered: