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
We have an application using rdkafka (version 0.36.2) that takes several minutes to shutdown. I've been attempting to make the shutdown process faster. So I've been trying to understand how StreamConsumer implements the shutdown/cleanup sequence after an unsubscribe is done.
there appears be a property internal.termination.signal exposed on librdkafka that can be used for expediting termination. This configured signal though appears to be used via consumer close though. From what I can tell StreamConsumer doesn't expose a close. Are there any suggestions for how to expedite StreamConsumer termination?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We have an application using rdkafka (version 0.36.2) that takes several minutes to shutdown. I've been attempting to make the shutdown process faster. So I've been trying to understand how StreamConsumer implements the shutdown/cleanup sequence after an
unsubscribeis done.From looking at
librdkafkadocumentation here https://github.com/confluentinc/librdkafka/blob/master/INTRODUCTION.md#speeding-up-terminationthere appears be a property
internal.termination.signalexposed on librdkafka that can be used for expediting termination. This configured signal though appears to be used via consumerclosethough. From what I can tellStreamConsumerdoesn't expose aclose. Are there any suggestions for how to expedite StreamConsumer termination?Beta Was this translation helpful? Give feedback.
All reactions