You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Florian Witteler (JIRA)" <ji...@apache.org> on 2016/09/30 13:05:20 UTC
[jira] [Created] (KAFKA-4238) consumer-subscription not working,
when accessing a newly created topic immediately after its creation with
the AdminUtils
Florian Witteler created KAFKA-4238:
---------------------------------------
Summary: consumer-subscription not working, when accessing a newly created topic immediately after its creation with the AdminUtils
Key: KAFKA-4238
URL: https://issues.apache.org/jira/browse/KAFKA-4238
Project: Kafka
Issue Type: Bug
Affects Versions: 0.10.0.1, 0.10.0.0
Reporter: Florian Witteler
I created a test-project to reproduce the bug.
https://github.com/FloWi/kafka-topic-creation-bug
We use a docker container that creates a fresh topic before a testsuite gets executed (see {{trait FreshKafkaTopics}}). That trait uses the AdminUtils to create the topic.
If we access the newly created topic directly after its creation, the subscriber is broken. It sometimes works though (<5%), so it seems to be a race-condition.
If I put a {{Thread.sleep(1000)}} after the topic-creation, everything's fine though.
So, the problem is twofold:
- {{AdminUtils.createTopic}} should block until the topic-creation is completed
- {{new KafkaConsumer[String, String](props).subscribe(util.Arrays.asList(topic))}} should throw an exception, when the topic is "not ready"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)