kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-3871) Transient test failure: testSimpleConsumption
Date Mon, 20 Jun 2016 11:25:05 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339362#comment-15339362
] 

Ismael Juma commented on KAFKA-3871:
------------------------------------

Thanks for the analysis. Sad that an easy fix is not available in this case (obvious producer
leak) . :)

> Transient test failure: testSimpleConsumption
> ---------------------------------------------
>
>                 Key: KAFKA-3871
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3871
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: unit tests
>    Affects Versions: 0.10.0.0
>            Reporter: Ismael Juma
>              Labels: transient-unit-test-failure
>
> {code}
> kafka.common.TopicExistsException: Topic "topic" already exists.
> 	at kafka.admin.AdminUtils$.createOrUpdateTopicPartitionAssignmentPathInZK(AdminUtils.scala:420)
> 	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:404)
> 	at kafka.utils.TestUtils$.createTopic(TestUtils.scala:237)
> 	at kafka.api.BaseConsumerTest.setUp(BaseConsumerTest.scala:63)
> {code}
> The following was printed to standard out:
> {code}
> [2016-06-16 23:57:44,161] ERROR [KafkaApi-0] Error when handling request {topics=[topic]}
(kafka.server.KafkaApis:103)
> kafka.admin.AdminOperationException: replication factor: 1 larger than available brokers:
0
> 	at kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:117)
> 	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:403)
> 	at kafka.server.KafkaApis.kafka$server$KafkaApis$$createTopic(KafkaApis.scala:629)
> 	at kafka.server.KafkaApis$$anonfun$29.apply(KafkaApis.scala:670)
> 	at kafka.server.KafkaApis$$anonfun$29.apply(KafkaApis.scala:666)
> 	at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
> 	at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
> 	at scala.collection.immutable.Set$Set1.foreach(Set.scala:74)
> 	at scala.collection.TraversableLike$class.map(TraversableLike.scala:244)
> 	at scala.collection.AbstractSet.scala$collection$SetLike$$super$map(Set.scala:47)
> 	at scala.collection.SetLike$class.map(SetLike.scala:93)
> 	at scala.collection.AbstractSet.map(Set.scala:47)
> 	at kafka.server.KafkaApis.getTopicMetadata(KafkaApis.scala:666)
> 	at kafka.server.KafkaApis.handleTopicMetadataRequest(KafkaApis.scala:727)
> 	at kafka.server.KafkaApis.handle(KafkaApis.scala:79)
> 	at kafka.server.KafkaRequestHandler.run(KafkaRequestHandler.scala:60)
> 	at java.lang.Thread.run(Thread.java:744)
> {code}
> Build link: https://builds.apache.org/job/kafka-trunk-jdk7/1371/
> [~rsivaram], do you think the root cause is the same as KAFKA-3217?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message