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
This StreamConsumer racy behavior can be observed in the recent release, probably after the move to Event-based API.
Some of the events (stats, logs etc.) are processed internally and are consumed by the poll returning None. Since librdkafka only wakes the queue when it transitions from empty -> non-empty, waker might be not called at any point in the future in this case.
Event order example:
new message event
new stats event
poll processes stats and returns None
StreamConsumer sets up waker and returns Poll::Pending
waker is never called by librdkafka since the queue never went empty
This
StreamConsumer
racy behavior can be observed in the recent release, probably after the move to Event-based API.Some of the events (stats, logs etc.) are processed internally and are consumed by the
poll
returningNone
. Sincelibrdkafka
only wakes the queue when it transitions from empty -> non-empty, waker might be not called at any point in the future in this case.Event order example:
poll
processes stats and returnsNone
StreamConsumer
sets up waker and returnsPoll::Pending
Probably connected issue: #638
The text was updated successfully, but these errors were encountered: