[
https://issues.apache.org/jira/browse/KAFKA-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16556757#comment-16556757
]
Matthias J. Sax commented on KAFKA-6520:
----------------------------------------
[~harjitdotsingh] If you want to work on this ticket, it's your call to make a
proposal :) If you want to make a full design before opening a PR, please
prepare a design document (similar to a KIP and we can discuss it). Otherwise,
you can also just open a PR and we discuss your proposal there during review.
> 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: Improvement
> Components: streams
> Reporter: Michael Kohout
> Assignee: Milind Jain
> Priority: Major
> Labels: newbie, user-experience
>
> 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)
