[
https://issues.apache.org/jira/browse/KAFKA-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15717780#comment-15717780
]
ASF GitHub Bot commented on KAFKA-4476:
---------------------------------------
GitHub user mjsax opened a pull request:
https://github.com/apache/kafka/pull/2209
KAFKA-4476: Kafka Streams gets stuck if metadata is missing
- break loop in StreamPartitionAssigner.assign() in case partition
metadata is missing
- fit state transition issue (follow up to KAFKA-3637: Add method that
checks if streams are initialised)
- some test improvements
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mjsax/kafka
kafka-4476-stuck-on-missing-metadata
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2209.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 #2209
----
commit 77598544bc5c2f9d0c967bcdda392c701ebacff7
Author: Matthias J. Sax <matth...@confluent.io>
Date: 2016-12-03T09:19:34Z
KAFKA-4476: Kafka Streams gets stuck if metadata is missing
- break loop in StreamPartitionAssigner.assign() in case partition
metadata is missing
- fit state transition issue (follow up to KAFKA-3637: Add method that
checks if streams are initialised)
- some test improvements
----
> Kafka Streams gets stuck if metadata is missing
> -----------------------------------------------
>
> Key: KAFKA-4476
> URL: https://issues.apache.org/jira/browse/KAFKA-4476
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Matthias J. Sax
> Assignee: Matthias J. Sax
> Priority: Critical
>
> When a Kafka Streams application gets started for the first time, it can
> happen that some topic metadata is missing when
> {{StreamPartitionAssigner#assign()}} is called on the group leader instance.
> This can result in an infinite loop within
> {{StreamPartitionAssigner#assign()}}. This issue was detected by
> {{ResetIntegrationTest}} that does have a transient timeout failure (c.f.
> https://issues.apache.org/jira/browse/KAFKA-4058 -- this issue was re-opened
> multiple times as the problem was expected to be in the test -- however, that
> is not the case).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
