pulsar

There are some workarounds..you could pass a list of topic names to the pulsar admin commands to delete the topics..also, take a look at the comments in this issue for some pointers

<https://github.com/apache/pulsar/issues/5554>

<https://pulsar.apache.org/admin-rest-api/#operation/deletePartitionedTopic>

also, to test this theory, can you send a sample topic name to try to replicate this..

`pulsar-admin topics delete Tenant/Namespace/Topic` accepts single topic in 2.11

I configured broker to allow force deleting whole namespace:
```forceDeleteNamespaceAllowed: 'true'```

but unfortunately:
```$ ./bin/pulsar-admin namespaces delete -f Tenant/Namespace
2023-01-31T10:45:27,760+0000 [AsyncHttpClient-7-1] WARN  org.apache.pulsar.client.admin.internal.BaseResource - [<https://pulsar.local/admin/v2/namespaces/Tenant/Namespace?force=true>] Failed to perform http delete request: javax.ws.rs.ClientErrorException: HTTP 414 URI Too Long
HTTP 414 URI Too Long

Reason: HTTP 414 URI Too Long```

so, The best way is to drain all the topics and wait until GC kicks to remove the topics

Topics get deleted when no producers and consumers and no backlog

<https://pulsar.apache.org/docs/next/admin-api-topics/#create>

Did you try deleting the entries for these from zookeeper?