[
https://issues.apache.org/jira/browse/KAFKA-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949128#comment-15949128
]
Magnus Edenhill commented on KAFKA-4476:
----------------------------------------
Directed here from KAFKA-4482.
Happened again on trunk PR:
https://builds.apache.org/job/kafka-pr-jdk8-scala2.11/2536/testReport/junit/org.apache.kafka.streams.integration/ResetIntegrationTest/testReprocessingFromScratchAfterResetWithoutIntermediateUserTopic/
> 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
> Fix For: 0.10.2.0
>
>
> 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.15#6346)
