You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Michael Kohout (JIRA)" <ji...@apache.org> on 2018/02/01 20:15:00 UTC
[jira] [Updated] (KAFKA-6520) When a Kafka Stream can't communicate
with the server, it's Status stays RUNNING
[ https://issues.apache.org/jira/browse/KAFKA-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Kohout updated KAFKA-6520:
----------------------------------
Description:
When you execute the following scenario the application is always in RUNNING state
1)start kafka
2)start app, app connects to kafka and starts processing
3)kill kafka(stop docker container)
4)the application doesn't give any indication that it's no longer connected(Stream State is still RUNNING, and the uncaught exception handler isn't invoked)
It would be useful if the Stream State had a DISCONNECTED status.
See [this|https://groups.google.com/forum/#!topic/confluent-platform/nQh2ohgdrIQ] for a discussion from the google user forum. [This|https://issues.apache.org/jira/browse/KAFKA-4564] is a link to a related issue.
was:
When you execute the following scenario the application is always in RUNNING state
1)start kafka
2)start app, app connects to kafka and starts processing
3)kill kafka(stop docker container)
4)the application doesn't give any indication that it's no longer connected(Stream State is still RUNNING, and the uncaught exception handler isn't invoked)
It would be useful if the Stream State had a DISCONNECTED status.
see [this|https://groups.google.com/forum/#!topic/confluent-platform/nQh2ohgdrIQ] for a discussion from the google user forum.
> When a Kafka Stream can't communicate with the server, it's Status stays RUNNING
> --------------------------------------------------------------------------------
>
> Key: KAFKA-6520
> URL: https://issues.apache.org/jira/browse/KAFKA-6520
> Project: Kafka
> Issue Type: Bug
> Reporter: Michael Kohout
> Priority: Major
>
> When you execute the following scenario the application is always in RUNNING state
>
> 1)start kafka
> 2)start app, app connects to kafka and starts processing
> 3)kill kafka(stop docker container)
> 4)the application doesn't give any indication that it's no longer connected(Stream State is still RUNNING, and the uncaught exception handler isn't invoked)
>
>
> It would be useful if the Stream State had a DISCONNECTED status.
>
> See [this|https://groups.google.com/forum/#!topic/confluent-platform/nQh2ohgdrIQ] for a discussion from the google user forum. [This|https://issues.apache.org/jira/browse/KAFKA-4564] is a link to a related issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)