You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Pradeep (JIRA)" <ji...@apache.org> on 2014/10/30 14:39:33 UTC

[jira] [Updated] (KAFKA-1738) Partition files not created after restart from forced shutdown

     [ https://issues.apache.org/jira/browse/KAFKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pradeep updated KAFKA-1738:
---------------------------
    Affects Version/s: 0.8.2

> Partition files not created after restart from forced shutdown
> --------------------------------------------------------------
>
>                 Key: KAFKA-1738
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1738
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8.1.1, 0.8.2
>         Environment: Linux, 2GB RAM, 2 Core CPU
>            Reporter: Pradeep
>
> We are using Kafka Topic APIs to create the topic. But in some cases, the topic gets created but we don't see the partition specific files and when producer/consumer tries to get the topic metadata and it fails with exception.
> k.p.BrokerPartitionInfo - Error while fetching metadata [{TopicMetadata for topic tloader1 -> No partition metadata for topic tloader1 due to kafka.common.UnknownTopicOrPartitionException}] for topic [tloader1]: class kafka.common.UnknownTopicOrPartitionException
> Steps to reproduce - 
> 1.      Stop kafka using kill  -9 <PID of Kafka>
> 2.      Start Kafka
> 3.      Create Topic with partition and replication factor of 1.
> 4.      Check the response “Created topic <topic_name>”
> 5.      Run the list command to verify if its created.
> 6.      Now check the data directory of kakfa. There would not be any for the newly created topic.



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