You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Vahid Hashemian (JIRA)" <ji...@apache.org> on 2017/02/23 23:57:44 UTC
[jira] [Created] (KAFKA-4795) Confusion around topic deletion
Vahid Hashemian created KAFKA-4795:
--------------------------------------
Summary: Confusion around topic deletion
Key: KAFKA-4795
URL: https://issues.apache.org/jira/browse/KAFKA-4795
Project: Kafka
Issue Type: Bug
Affects Versions: 0.10.2.0
Reporter: Vahid Hashemian
Assignee: Vahid Hashemian
The topic deletion works like in 0.10.2.0:
# {{bin/zookeeper-server-start.sh config/zookeeper.properties}}
# {{bin/kafka-server-start.sh config/server.properties}} (uses default {{server.properties}})
# {{bin/kafka-topics.sh --zookeeper localhost:2181 --create --topic test --replication-factor 1 --partitions 1}} (creates the topic {{test}})
# {{bin/kafka-topics.sh --zookeeper localhost:2181 --list}} (returns {{test}})
# {{bin/kafka-topics.sh --zookeeper localhost:2181 --delete --topic test}} (reports {{Topic test is marked for deletion. Note: This will have no impact if delete.topic.enable is not set to true.}})
# {{bin/kafka-topics.sh --zookeeper localhost:2181 --list}} (returns {{test}})
Previously, the last command above returned {{test - marked for deletion}}, which matched the output statement of the {{--delete}} topic command.
Continuing with the above scenario,
# stop the broker
# add the broker config {{delete.topic.enable=true}} in the config file
# {{bin/kafka-server-start.sh config/server.properties}} (this does not remove the topic {{test}}, as if the topic was never marked for deletion).
# {{bin/kafka-topics.sh --zookeeper localhost:2181 --delete --topic test}} (reports {{Topic test is marked for deletion. Note: This will have no impact if delete.topic.enable is not set to true.}})
# {{bin/kafka-topics.sh --zookeeper localhost:2181 --list}} (returns no topics).
It seems that the "marked for deletion" state for topics no longer exists.
I opened this JIRA so I can get a confirmation on the expected topic deletion behavior, because in any case, I think the user experience could be improved (either there is a bug in the code, or the command's output statement is misleading).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)