You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/12/14 14:10:01 UTC
[GitHub] [pulsar] sixhj commented on issue #8954: func Namespace does not have any clusters configured
sixhj commented on issue #8954:
URL: https://github.com/apache/pulsar/issues/8954#issuecomment-744464962
Troubleshooting
Error message: Namespace missing local cluster name in clusters list
Failed to get partitioned topic metadata: org.apache.pulsar.client.api.PulsarClientException$BrokerMetadataException: Namespace missing local cluster name in clusters list: local_cluster=xyz ns=public/functions clusters=[standalone]
The error message prompts when either of the cases occurs:
a) a broker is started with functionsWorkerEnabled=true, but the pulsarFunctionsCluster is not set to the correct cluster in the conf/functions_worker.yaml file;
b) setting up a geo-replicated Pulsar cluster with functionsWorkerEnabled=true, while brokers in one cluster run well, brokers in the other cluster do not work well.
Workaround
If any of these cases happens, follow the instructions below to fix the problem:
Get the current clusters list of public/functions namespace.
bin/pulsar-admin namespaces get-clusters public/functions
Check if the cluster is in the clusters list. If the cluster is not in the list, add it to the list and update the clusters list.
bin/pulsar-admin namespaces set-clusters --cluster=<existing-clusters>,<new-cluster> public/functions
Set the correct cluster name in pulsarFunctionsCluster in the conf/functions_worker.yml file.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org