[
https://issues.apache.org/jira/browse/KAFKA-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon updated KAFKA-2094:
--------------------------------
Description:
After I create a topic and then remove it (and wait for enough time to
eventually delete it), it does not create a topic emitting errors even though
auto-create topic option is true. It works okay when I manually create a topic
after deleting it.
Here is the command I run.
./bin/kafka-topics.sh --list --zookeeper 192.168.0.190:2181
test
./bin/kafka-topics.sh --delete --zookeeper 192.168.0.190:2181 --topic test
bin/kafka-console-producer.sh --broker-list localhost:9092 --topic test
[2015-04-06 20:51:44,542] WARN Property topic is not valid
(kafka.utils.VerifiableProperties)
test
[2015-04-06 20:51:49,896] WARN Error while fetching metadata [{TopicMetadata
for topic test ->
No partition metadata for topic test due to
kafka.common.LeaderNotAvailableException}] for topic [test]: class
kafka.common.LeaderNotAvailableException (kafka.producer.BrokerPartitionInfo)
[2015-04-06 20:51:49,904] WARN Error while fetching metadata [{TopicMetadata
for topic test->
No partition metadata for topic testdue to
kafka.common.LeaderNotAvailableException}] for topic [test]: class
kafka.common.LeaderNotAvailableException (kafka.producer.BrokerPartitionInfo)
[2015-04-06 20:51:49,905] ERROR Failed to collate messages by topic, partition
due to: Failed to fetch topic metadata for topic:
test(kafka.producer.async.DefaultEventHandler)
^Csnowdrop@master:~/workspace/kafka/kafka_2.10-0.8.2.0$
bin/kafka-console-producer.sh --broker-list localhost:9092 --topic test
[2015-04-06 20:52:08,733] WARN Property topic is not valid
(kafka.utils.VerifiableProperties)
Server side, I got this error
[2015-04-06 21:41:08,491] ERROR [Replica Manager on Broker 0]: Error when
processing fetch request for partition [test,0] offset 1687 from consumer with
correlation id 5. Possible cause: Request for offset 1687 but we only have log
segments in the range 0 to 107. (kafka.server.ReplicaManager)
was:
After I create a topic and then remove it (and wait for enough time to
eventually delete it), it does not create a topic emitting errors even though
auto-create topic option is true. It works okay when I manually create a topic
after deleting it.
Here is the command I run.
./bin/kafka-topics.sh --list --zookeeper 192.168.0.190:2181
test
./bin/kafka-topics.sh --delete --zookeeper 192.168.0.190:2181 --topic test
bin/kafka-console-producer.sh --broker-list localhost:9092 --topic test
[2015-04-06 20:51:44,542] WARN Property topic is not valid
(kafka.utils.VerifiableProperties)
test
[2015-04-06 20:51:49,896] WARN Error while fetching metadata [{TopicMetadata
for topic test ->
No partition metadata for topic test due to
kafka.common.LeaderNotAvailableException}] for topic [test]: class
kafka.common.LeaderNotAvailableException (kafka.producer.BrokerPartitionInfo)
[2015-04-06 20:51:49,904] WARN Error while fetching metadata [{TopicMetadata
for topic test->
No partition metadata for topic testdue to
kafka.common.LeaderNotAvailableException}] for topic [test]: class
kafka.common.LeaderNotAvailableException (kafka.producer.BrokerPartitionInfo)
[2015-04-06 20:51:49,905] ERROR Failed to collate messages by topic, partition
due to: Failed to fetch topic metadata for topic:
test(kafka.producer.async.DefaultEventHandler)
^Csnowdrop@master:~/workspace/kafka/kafka_2.10-0.8.2.0$
bin/kafka-console-producer.sh --broker-list localhost:9092 --topic test
[2015-04-06 20:52:08,733] WARN Property topic is not valid
(kafka.utils.VerifiableProperties)
Server side, I got this error
[2015-04-06 21:41:08,491] ERROR [Replica Manager on Broker 0]: Error when
processing fetch request for partition [lavender_0_1,0] offset 1687 from
consumer with correlation id 5. Possible cause: Request for offset 1687 but we
only have log segments in the range 0 to 107. (kafka.server.ReplicaManager)
> Kafka does not create topic automatically after deleting the topic.
> -------------------------------------------------------------------
>
> Key: KAFKA-2094
> URL: https://issues.apache.org/jira/browse/KAFKA-2094
> Project: Kafka
> Issue Type: Bug
> Components: admin
> Affects Versions: 0.8.2.0
> Environment: Ubuntu 14.04 LTS
> Reporter: Hyukjin Kwon
> Priority: Critical
>
> After I create a topic and then remove it (and wait for enough time to
> eventually delete it), it does not create a topic emitting errors even though
> auto-create topic option is true. It works okay when I manually create a
> topic after deleting it.
> Here is the command I run.
> ./bin/kafka-topics.sh --list --zookeeper 192.168.0.190:2181
> test
> ./bin/kafka-topics.sh --delete --zookeeper 192.168.0.190:2181 --topic test
> bin/kafka-console-producer.sh --broker-list localhost:9092 --topic test
> [2015-04-06 20:51:44,542] WARN Property topic is not valid
> (kafka.utils.VerifiableProperties)
> test
> [2015-04-06 20:51:49,896] WARN Error while fetching metadata [{TopicMetadata
> for topic test ->
> No partition metadata for topic test due to
> kafka.common.LeaderNotAvailableException}] for topic [test]: class
> kafka.common.LeaderNotAvailableException (kafka.producer.BrokerPartitionInfo)
> [2015-04-06 20:51:49,904] WARN Error while fetching metadata [{TopicMetadata
> for topic test->
> No partition metadata for topic testdue to
> kafka.common.LeaderNotAvailableException}] for topic [test]: class
> kafka.common.LeaderNotAvailableException (kafka.producer.BrokerPartitionInfo)
> [2015-04-06 20:51:49,905] ERROR Failed to collate messages by topic,
> partition due to: Failed to fetch topic metadata for topic:
> test(kafka.producer.async.DefaultEventHandler)
> ^Csnowdrop@master:~/workspace/kafka/kafka_2.10-0.8.2.0$
> bin/kafka-console-producer.sh --broker-list localhost:9092 --topic test
> [2015-04-06 20:52:08,733] WARN Property topic is not valid
> (kafka.utils.VerifiableProperties)
> Server side, I got this error
> [2015-04-06 21:41:08,491] ERROR [Replica Manager on Broker 0]: Error when
> processing fetch request for partition [test,0] offset 1687 from consumer
> with correlation id 5. Possible cause: Request for offset 1687 but we only
> have log segments in the range 0 to 107. (kafka.server.ReplicaManager)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
