You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Vahid Hashemian (JIRA)" <ji...@apache.org> on 2018/11/11 03:52:00 UTC
[jira] [Resolved] (KAFKA-7604) Flaky Test
`ConsumerCoordinatorTest.testRebalanceAfterTopicUnavailableWithPatternSubscribe`
[ https://issues.apache.org/jira/browse/KAFKA-7604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vahid Hashemian resolved KAFKA-7604.
------------------------------------
Resolution: Fixed
> Flaky Test `ConsumerCoordinatorTest.testRebalanceAfterTopicUnavailableWithPatternSubscribe`
> -------------------------------------------------------------------------------------------
>
> Key: KAFKA-7604
> URL: https://issues.apache.org/jira/browse/KAFKA-7604
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Major
>
> {code}
> java.lang.AssertionError: Metadata refresh requested unnecessarily
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at org.apache.kafka.clients.consumer.internals.ConsumerCoordinatorTest.unavailableTopicTest(ConsumerCoordinatorTest.java:1034)
> at org.apache.kafka.clients.consumer.internals.ConsumerCoordinatorTest.testRebalanceAfterTopicUnavailableWithPatternSubscribe(ConsumerCoordinatorTest.java:984)
> {code}
> The problem seems to be a race condition in the test case with the heartbeat thread and the foreground thread unsafely attempting to update metadata at the same time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)