[GitHub] [incubator-pulsar] sijie opened issue #2430: Namespaces admin commands should be able to distinguish v1 and v2 namespace format

["sijie (GitHub)" <gi...@apache.org>]

#### Expected behavior

- setup a 2.0.0 cluster
- enable backlog : set-backlog-quotas test-tenant/test-cluster/ns1 --limit 500G --policy producer_exception
- run perf: pulsar-perf produce persistent://test-tenant/test-cluster/ns1/test-topic
- pulsar perf should be able to produce 500G data

#### Actual behavior

- pulsar perf encounters backlog exception when producing around ~10GB data

#### Steps to reproduce

as described in "expected behavior"

#### System configuration
**Pulsar version**: 2.0.0


[ Full content available at: https://github.com/apache/incubator-pulsar/issues/2430 ]
This message was relayed via gitbox.apache.org for devnull@infra.apache.org

[GitHub] [incubator-pulsar] sijie commented on issue #2430: Namespaces admin commands should be able to distinguish v1 and v2 namespace format

["sijie (GitHub)" <gi...@apache.org>]

the problem is namespace admin commands don't distinguish v1 and v2 format. so set-backlog-quotas is setting the quota in a wrong namespace.  since the v2 topic name is limited to (tenant)/(namespace)/(topic), we should be able to distinguish v1 and v2 namespace name in admin commands. if it has only 2 components `(tenant)/(topic)`, it is a v2 namespace. we can simply disallow v1 namespace name in namespace admin commands.

[ Full content available at: https://github.com/apache/incubator-pulsar/issues/2430 ]
This message was relayed via gitbox.apache.org for devnull@infra.apache.org