[
https://issues.apache.org/jira/browse/KAFKA-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023760#comment-16023760
]
ASF GitHub Bot commented on KAFKA-5309:
---------------------------------------
GitHub user mjsax opened a pull request:
https://github.com/apache/kafka/pull/3140
KAFKA-5309: Stores not queryable after one thread died
- introduces a new thread state DEAD
- ignores DEAD threads when querying
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mjsax/kafka kafka-5309-stores-not-queryable
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/3140.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3140
----
commit d4fe00bcf401d493595e26d4077060d5edb6878a
Author: Matthias J. Sax <matth...@confluent.io>
Date: 2017-05-24T20:17:37Z
KAFKA-5309: Stores not queryable after one thread died
- introduces a new thread state DEAD
- ignores DEAD threads when querying
----
> Stores not queryable after one thread died
> ------------------------------------------
>
> Key: KAFKA-5309
> URL: https://issues.apache.org/jira/browse/KAFKA-5309
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 0.10.2.1
> Reporter: Matthias J. Sax
> Assignee: Matthias J. Sax
>
> For a multi threaded Streams instance, it can happen that one thread dies
> while all other threads (within a single instance) keep running. Even if this
> is an rare scenario, we should allow querying the stores after rebalance
> finished. However, this does never happen, as the died thread's state is
> still in {{KafkaStreams}} thread state map (as {{NOT_RUNNING}}), and thus,
> {{KafkaStreams}} itself is in state {{REBALANCING}} all the time and does not
> transit back to {{RUNNING}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
