[jira] [Commented] (KAFKA-784) creating topic without partitions, deleting then creating with partition causes errors in 'kafka-list-topic'

["Neha Narkhede (JIRA)" <ji...@apache.org>]

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

Neha Narkhede commented on KAFKA-784:
-------------------------------------

The delete topic functionality is not yet implemented in Kafka. Somehow a half baked version made it to the 0.8 branch. We plan to do this before release, we can revisit this at that time.
                
> creating topic without partitions, deleting then creating with partition causes errors in 'kafka-list-topic'
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-784
>                 URL: https://issues.apache.org/jira/browse/KAFKA-784
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8
>         Environment: 0.8.0 head as of 3/4/2013
>            Reporter: Chris Curtin
>            Priority: Minor
>
> Create a new topic using the command line:
> ./kafka-create-topic.sh --topic trash-1 --replica 3 --zookeeper localhost
> Realize you forgot to add the partition command, so remove it:
> ./kafka-delete-topic.sh --topic trash-1 --zookeeper localhost
> Recreate it with partitions:
> ./kafka-create-topic.sh --topic trash-1 --replica 3 --zookeeper localhost --partition 5
> Try to get a listing:
> ./kafka-list-topic.sh --topic trash-1 --zookeeper localhost
> Errors:
> [2013-03-04 14:15:23,876] ERROR Error while fetching metadata for partition [trash-1,0] (kafka.admin.AdminUtils$)
> kafka.common.LeaderNotAvailableException: Leader not available for topic trash-1 partition 0
>         at kafka.admin.AdminUtils$$anonfun$3.apply(AdminUtils.scala:120)
>         at kafka.admin.AdminUtils$$anonfun$3.apply(AdminUtils.scala:103)
>         at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:206)
>         at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:206)
>         at scala.collection.LinearSeqOptimized$class.foreach(LinearSeqOptimized.scala:61)
>         at scala.collection.immutable.List.foreach(List.scala:45)
>         at scala.collection.TraversableLike$class.map(TraversableLike.scala:206)
>         at scala.collection.immutable.List.map(List.scala:45)
>         at kafka.admin.AdminUtils$.kafka$admin$AdminUtils$$fetchTopicMetadataFromZk(AdminUtils.scala:103)
>         at kafka.admin.AdminUtils$.fetchTopicMetadataFromZk(AdminUtils.scala:92)
>         at kafka.admin.ListTopicCommand$.showTopic(ListTopicCommand.scala:80)
>         at kafka.admin.ListTopicCommand$$anonfun$main$2.apply(ListTopicCommand.scala:66)
>         at kafka.admin.ListTopicCommand$$anonfun$main$2.apply(ListTopicCommand.scala:65)
>         at scala.collection.LinearSeqOptimized$class.foreach(LinearSeqOptimized.scala:61)
>         at scala.collection.immutable.List.foreach(List.scala:45)
>         at kafka.admin.ListTopicCommand$.main(ListTopicCommand.scala:65)
>         at kafka.admin.ListTopicCommand.main(ListTopicCommand.scala)
> Caused by: kafka.common.LeaderNotAvailableException: No leader exists for partition 0
>         at kafka.admin.AdminUtils$$anonfun$3.apply(AdminUtils.scala:117)
>         ... 16 more
> topic: trash-1
> PartitionMetadata(0,None,List(),List(),5)
> Can't recover until you restart all the Brokers in the cluster. Then the list command works correctly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira