[
https://issues.apache.org/jira/browse/KAFKA-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363724#comment-15363724
]
Bill Bejeck commented on KAFKA-3926:
------------------------------------
Looking at this a bit more. The test in question is failing on the first
assertion to confirm that both created topics are matched by the regex as
source topics. There is implicit assumption that all topics will be included
in the the call to create the stream tasks after the rebalance. But there
could actually be two calls, one with TEST-TOPIC-A, then another with both
topics. To fix the transient failures in this case I think the
waitForCondition call should be checking for all expected assigned topics vs
simply storing results of each call.
> Transient failures in
> org.apache.kafka.streams.integration.RegexSourceIntegrationTest
> -------------------------------------------------------------------------------------
>
> Key: KAFKA-3926
> URL: https://issues.apache.org/jira/browse/KAFKA-3926
> Project: Kafka
> Issue Type: Sub-task
> Components: streams, unit tests
> Reporter: Guozhang Wang
> Assignee: Bill Bejeck
>
> {code}
> org.apache.kafka.streams.integration.RegexSourceIntegrationTest >
> testRegexMatchesTopicsAWhenDeleted FAILED
> java.lang.AssertionError:
> Expected: <[TEST-TOPIC-A, TEST-TOPIC-B]>
> but: was <[TEST-TOPIC-A]>
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.junit.Assert.assertThat(Assert.java:956)
> at org.junit.Assert.assertThat(Assert.java:923)
> at
> org.apache.kafka.streams.integration.RegexSourceIntegrationTest.testRegexMatchesTopicsAWhenDeleted(RegexSourceIntegrationTest.java:211)
> {code}
> I think it is due to the fact that some times the rebalance takes much longer
> than the specified 60 seconds.
> One example: https://builds.apache.org/job/kafka-trunk-jdk8/730/consoleFull
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
