-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Open
Labels
lifecycle/staletype/bugThe PR fixed a bug or issue reported a bugThe PR fixed a bug or issue reported a bug
Description
Describe the bug
Pulsar enables brokerDeleteInactiveTopicsEnabled by default. However, for partitioned topics, if a topic was de
To Reproduce
Steps to reproduce the behavior:
- Modify the
conf/standalone.conf
# How often to check for inactive topics
brokerDeleteInactiveTopicsFrequencySeconds=10- Start a standalone
bin/pulsar standalone- Create a partitioned topic
bin/pulsar-admin topics create-partitioned-topic my-topic -p 3- Produce a message, otherwise the topic won't be deleted (I'm not sure if this behavior is right)
./bin/pulsar-client produce -m hello my-topic- Wait for at least 10 seconds, then list the topics
$ ./bin/pulsar-admin topics list public/default
$ ./bin/pulsar-admin topics create-partitioned-topic my-topic -p 3
20:01:41.196 [AsyncHttpClient-7-1] WARN org.apache.pulsar.client.admin.internal.BaseResource - [http://localhost:8080/admin/v2/persistent/public/default/my-topic/partitions] Failed to perform http put request: javax.ws.rs.ClientErrorException: HTTP 409 Conflict
Partitioned topic already exists
Reason: Partitioned topic already existsExpected behavior
After the partitioned topic is deleted, the metadata should be removed as well.
Desktop (please complete the following information):
- OS: MacOS
Metadata
Metadata
Assignees
Labels
lifecycle/staletype/bugThe PR fixed a bug or issue reported a bugThe PR fixed a bug or issue reported a bug