[
https://issues.apache.org/jira/browse/KAFKA-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394652#comment-16394652
]
Matthias J. Sax commented on KAFKA-6520:
----------------------------------------
[~milindjain], welcome to the community and thanks for you interest in
contributing to Kafka!
I added you to the list of contributors. This allows you to assign JIRAs to
yourself. So feel free to grab any unassigned Jira you want to work on.
About the ticket itself, I never thought how this could be resolved. Maybe it's
a good start to try to reproduce the issue locally by running a broker,
starting a Kafka Streams application in you IDE, stop the broker to figure out
how the app behaves. A good starting point would to look into
{{StreamThead#run()}} method. Also, check out this wiki page that describes the
architecture of the library to some extend:
[https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Streams+Architecture]
If you are completely new to Kafka, you should familiarize yourself with the
basic abstraction of brokers, topic, partitions, clients, consumer groups,
group rebalance first. There is tons of material online. Let us know if you
need any other help to get started.
Also check out [https://kafka.apache.org/contributing]
> 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)
