[
https://issues.apache.org/jira/browse/KAFKA-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823329#comment-15823329
]
huxi commented on KAFKA-4629:
-----------------------------
[~alberto.fo...@natwestmarkets.com] Yes, multiple brokers DOES help reproducing
the issue. And some interesting things were found. If deleting topic command
was issued right after creating the topic, some MBeans at the topic level
indeed failed to get removed. But if some delay time was put on between these
two commands, then all the topic-level MBeans could be removed as expected. In
the former case, the controller is still doing many background tasks to
complete the topic creation although the CREATE command returns successfully.
So could you wait some time before issuing the delete command to see whether
you would run into this issue?
> Per topic MBeans leak
> ---------------------
>
> Key: KAFKA-4629
> URL: https://issues.apache.org/jira/browse/KAFKA-4629
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.0.1
> Reporter: Alberto Forti
> Priority: Minor
>
> Hi,
> In our application we create and delete topics dynamically. Most of the times
> when a topic is deleted the related MBeans are not deleted. Example of MBean:
> kafka.server:type=BrokerTopicMetrics,name=TotalProduceRequestsPerSec,topic=dw_06b5f828-e452-4e22-89c9-67849a65603d
> Also, deleting a topic often produces (what I think is) noise in the logs at
> WARN level. One example is:
> WARN PartitionStateMachine$DeleteTopicsListener:83 - [DeleteTopicsListener
> on 1]: Ignoring request to delete non-existing topics
> dw_fe8ff14b-aa9b-4f24-9bc1-6fbce15d20d2
> Easy reproducible with a basic Kafka cluster with two brokers, just create
> and delete topics few times. Sometimes the MBeans for the topic are deleted
> and sometimes are not.
> I'm creating and deleting topics using the AdminUtils class in the Java API:
> AdminUtils.deleteTopic(zkUtils, topicName);
> AdminUtils.createTopic(zkUtils, topicName, partitions, replicationFactor,
> topicConfiguration, kafka.admin.RackAwareMode.Enforced$.MODULE$);
> Kafka version: 0.10.0.1 (haven't tried other versions)
> Thanks,
> Alberto
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
