[
https://issues.apache.org/jira/browse/KAFKA-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16556958#comment-16556958
]
Matthias J. Sax commented on KAFKA-6520:
----------------------------------------
No worries. All good :)
A KIP is a "Kafka Improvement Proposal":
[https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals]
It's only required for major features and public API changes. This ticket does
not need a KIP. Thus, you should not start a DISCUSS thread and voting is not
required either. It might just be helpful to do a similar writeup (could be a
google doc) for the design – might help to get "your feet wet" as you phrased
it. If you don't want to do it, it's fine, too. I recommend it, as it seems to
be more efficient if you do a full design instead and ask all open question at
once if you have any instead of individual questions going forth and back in
the comment section on the ticket. Let us know if you need any help.
> 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)
