-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SubSourceLogic may send Stop twice #526
Comments
This may not be the same issue, but I observe similar behavior with the SingleSourceLogic component. Using akka-stream-kafka v2.0.5. BaseSingleSourceLogic.scala:114 will cause the function performShutdown() in SingleSourceLogic.scala:48 which will shut down the consumer actor. After this is done the postStop function in SingleSourceLogic.scala:44 will send a StopFromStage message to the (already killed) consumer actor, which causes a dead letter message to appear in the logs. Repro pseudocode: Setting the config akka.kafka.consumer.stop-timeout = 0 will force this issue. Using the default akka.kafka.consumer.stop-timeout = 30 will also reproduce the issue, it's just that in that case it will be the delayed StopFromStage message coming from SingleSourceLogic.scala:67 which will trigger the dead letter message, since the postStop SingleSourceLogic.scala:44 would have run first. |
Thank you for sharing your observations. It is the same issue indeed. |
When using the
ConsumerControl
to stop a consumer theStop
message may be sent twice to theKafkaConsumerActor
resulting in a dead letter.Both
SubSourceLogic.performShutdown
andSubSourceLogic.postStop
sendStop
.The text was updated successfully, but these errors were encountered: