[ https://issues.apache.org/jira/browse/KAFKA-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manikumar Reddy reassigned KAFKA-4074: -------------------------------------- Assignee: Manikumar Reddy > Deleting a topic can make it unavailable even if delete.topic.enable is false > ----------------------------------------------------------------------------- > > Key: KAFKA-4074 > URL: https://issues.apache.org/jira/browse/KAFKA-4074 > Project: Kafka > Issue Type: Bug > Components: controller > Reporter: Joel Koshy > Assignee: Manikumar Reddy > Fix For: 0.10.1.0 > > > The {{delete.topic.enable}} configuration does not completely block the > effects of delete topic since the controller may (indirectly) query the list > of topics under the delete-topic znode. > To reproduce: > * Delete topic X > * Force a controller move (either by bouncing or removing the controller > znode) > * The new controller will send out UpdateMetadataRequests with leader=-2 for > the partitions of X > * Producers eventually stop producing to that topic > The reason for this is that when ControllerChannelManager adds > UpdateMetadataRequests for brokers, we directly use the partitionsToBeDeleted > field of the DeleteTopicManager (which is set to the partitions of the topics > under the delete-topic znode on controller startup). > In order to get out of the situation you have to remove X from the znode and > then force another controller move. -- This message was sent by Atlassian JIRA (v6.3.4#6332)