You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/09/27 03:24:20 UTC
[jira] [Commented] (KAFKA-3175) topic not accessible after deletion
even when delete.topic.enable is disabled
[ https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15524915#comment-15524915 ]
ASF GitHub Bot commented on KAFKA-3175:
---------------------------------------
GitHub user MayureshGharat opened a pull request:
https://github.com/apache/kafka/pull/1913
KAFKA-3175 (Rebased) : topic not accessible after deletion even when delete.topic.enable is disabled
Rebased the patch with current trunk.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MayureshGharat/kafka kafka-3175_latest
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1913.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1913
----
commit 3b4412eb948318ac8fbea855ff52071bbb6f8fb3
Author: MayureshGharat <gh...@gmail.com>
Date: 2016-02-01T21:51:57Z
Remove topics under /admin/delete_topics path in zk if deleteTopic is disabled. The topic should never be enqueued for deletion
commit 1bf29ae00da0eaa0044bdc1bb8dc6cc80ee90951
Author: MayureshGharat <gh...@gmail.com>
Date: 2016-03-11T17:25:32Z
Addressed Jun's comment to clean the zk state for a topic on cluster restart and delete topic disabled
----
> topic not accessible after deletion even when delete.topic.enable is disabled
> -----------------------------------------------------------------------------
>
> Key: KAFKA-3175
> URL: https://issues.apache.org/jira/browse/KAFKA-3175
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.9.0.0
> Reporter: Jun Rao
> Assignee: Mayuresh Gharat
> Fix For: 0.10.1.0
>
>
> The can be reproduced with the following steps.
> 1. start ZK and 1 broker (with default delete.topic.enable=false)
> 2. create a topic test
> bin/kafka-topics.sh --zookeeper localhost:2181 --create --topic test --partition 1 --replication-factor 1
> 3. delete topic test
> bin/kafka-topics.sh --zookeeper localhost:2181 --delete --topic test
> 4. restart the broker
> Now topic test still shows up during topic description.
> bin/kafka-topics.sh --zookeeper localhost:2181 --describe
> Topic:test PartitionCount:1 ReplicationFactor:1 Configs:
> Topic: test Partition: 0 Leader: 0 Replicas: 0 Isr: 0
> However, one can't produce to this topic any more.
> bin/kafka-console-producer.sh --broker-list localhost:9092 --topic test
> [2016-01-29 17:55:24,527] WARN Error while fetching metadata with correlation id 0 : {test=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
> [2016-01-29 17:55:24,725] WARN Error while fetching metadata with correlation id 1 : {test=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
> [2016-01-29 17:55:24,828] WARN Error while fetching metadata with correlation id 2 : {test=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)