[Bug] Replication clusters cannot be cleared for a namespace

[omarkj]

Search before reporting

• I searched in the issues and found nothing similar.

Read release policy

• I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

User environment

Pulsar 4.0.5

Issue Description

Apache Pulsar allows replication clusters to be set at the namespace level. This means every topic in a namespace gets replicated as configured.

To date there is no way to disable replication at the namespace level. If an empty list of clusters is passed in, Pulsar returns an error:

 curl -XPOST  https://:CLUSTER_ENDPOINT/admin/v2/:TENANT/:NS/:TOPIC/replication -D '[]'
{"reason":"ClusterIds should not be null or empty"}

The expectation is for this to disable replication.

Error messages

{"reason":"ClusterIds should not be null or empty"}

Reproducing the issue

Apache Pulsar allows replication clusters to be set at the namespace level. This means every topic in a namespace gets replicated as configured.

To date there is no way to disable replication at the namespace level. If an empty list of clusters is passed in, Pulsar returns an error:

 curl -XPOST  https://:CLUSTER_ENDPOINT/admin/v2/:TENANT/:NS/:TOPIC/replication -D '[]'
{"reason":"ClusterIds should not be null or empty"}

The expectation is for this to disable replication.

Additional information

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!

[omarkj]

The checks for empty clusters got introduced in these two PRs:

At the topic level: #22537
At the namespace level: #21650

[poorbarcode]

@omarkj

You can remove namespace-level replication with the following command

pulsar-admin namespaces set-clusters -c <current-cluster, which can get from broker.cocnf -> clusterName> <namespace name>

[lhotari]

@omarkj

You can remove namespace-level replication with the following command

pulsar-admin namespaces set-clusters -c <current-cluster, which can get from broker.cocnf -> clusterName> <namespace name>

@poorbarcode What are the consequences of this after PIP-422? What are the rules for deleting topics when replication clusters get updated?

[omarkj]

@omarkj

You can remove namespace-level replication with the following command

pulsar-admin namespaces set-clusters -c <current-cluster, which can get from broker.cocnf -> clusterName> <namespace name>

I did try this, but I causes the topic to be deleted on the removed cluster. What I’m looking to do is keep the topic on both clusters, just disable replication.