-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pulsar broker start failure when set functionsWorkerEnabled=true #2328
Comments
Found the reason for this issue. In zookeeper data of path named " /admin/policies/public/functions" has "replication_clusters":["standalone"] When i set it to my cluster name "pulsar-qa". I can start the broker success. |
To change config pulsarFunctionsCluster in functions_worker.yml |
@codelipenghui that's correct. the |
Closed the issue. Since the problem was addressed by updating |
Seems to be a mistake in the PR referenced. |
I have this same issue with running Pulsar on Kubernetes. I see that the script |
…th broker (#10552) ### Motivation When start function worker with broker, we need to set pulsarFunctionsCluster in functions_worker.yml, other wise it will fail to start. #2328 If we run broker in k8s, we should set correct config map to change the default value in functions_worker.yml. In this mode, pulsarFunctionsCluster should always be same with the cluster name in broker.conf, so we can get the setting directly from broker.conf. ### Modifications get function cluster from broker config when start function worker with broker
…th broker (apache#10552) ### Motivation When start function worker with broker, we need to set pulsarFunctionsCluster in functions_worker.yml, other wise it will fail to start. apache#2328 If we run broker in k8s, we should set correct config map to change the default value in functions_worker.yml. In this mode, pulsarFunctionsCluster should always be same with the cluster name in broker.conf, so we can get the setting directly from broker.conf. ### Modifications get function cluster from broker config when start function worker with broker
…th broker (apache#10552) ### Motivation When start function worker with broker, we need to set pulsarFunctionsCluster in functions_worker.yml, other wise it will fail to start. apache#2328 If we run broker in k8s, we should set correct config map to change the default value in functions_worker.yml. In this mode, pulsarFunctionsCluster should always be same with the cluster name in broker.conf, so we can get the setting directly from broker.conf. ### Modifications get function cluster from broker config when start function worker with broker
When i set functionsWorkerEnabled=true
I got exception like this:
My broker conf:
The text was updated successfully, but these errors were encountered: