Zhen-hao opened a new issue #11356: URL: https://github.com/apache/pulsar/issues/11356
See my console output: ``` [root@server2:~]# pulsar-admin namespaces list pairtime-test "pairtime-test/projection_akka_journal_nt_cluster_run_7" [root@server2:~]# pulsar-admin namespaces get-clusters pairtime-test/projection_akka_journal_nt_cluster_run_7 "pulsar-cluster-1" ``` `pulsar-cluster-1` was the cluster name I used in the first deployment, which was changed to `pairtime-test` in later deployments. Somehow the first name is sticky to namespaces created under that name. And in the [documentation page](https://pulsar.apache.org/docs/en/pulsar-admin/#get-clusters), it says "replication clusters". It seems all the settings around the cluster name make sense only in a geo-replication setup. However, the above mismatch cause runtime errors like ``` org.apache.pulsar.client.api.PulsarClientException$BrokerMetadataException: Namespace missing local cluster name in clusters list: local_cluster=nt-test-cluster ns=pairtime-test/projection_akka_journal_nt_cluster_run_7 clusters=[pulsar-cluster-1] at org.apache.pulsar.client.impl.ClientCnx.getPulsarClientException(ClientCnx.java:1092) at org.apache.pulsar.client.impl.ClientCnx.handlePartitionResponse(ClientCnx.java:589) at org.apache.pulsar.common.protocol.PulsarDecoder.channelRead(PulsarDecoder.java:129) ``` In a single cluster setup. **Posible fix:** 1. Make it very clear what the cluster name means to a namespace, and what operational steps are needed when the user changes the cluster name in a single-cluster setup. 2. Or, handle the above error internally and make it always work in a single-cluster setup. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
