Pulsar on k8s: broker start failure when set functionsWorkerEnabled=true
See original GitHub issueDescribe the bug
The Kubernetes deployment sets PF_pulsarFunctionsCluster
but this doesn’t appear to get applied to conf/functions_worker.yml
.
Looking at the source, it appears that the script gen-yml-from-env.py
is supposed to update functions_worker.yml
, but I think the script is missing the value pulsarFunctionsCluster
in INT_KEYS here: https://github.com/apache/pulsar/blob/60d2bfa389815b1769b36a0158059bfc3372a9a0/docker/pulsar/scripts/gen-yml-from-env.py#L30-L38
This is a followup to issue https://github.com/apache/pulsar/issues/2328.
Issue Analytics
- State:
- Created 4 years ago
- Comments:13 (8 by maintainers)
Top Results From Across the Web
Deploy and manage functions worker - Apache Pulsar
pulsarFunctionsCluster : Set the value to your Pulsar cluster name (same as the clusterName setting in the broker configuration). If authentication is enabled ......
Read more >Failing to set up Zookeeper cluster for Pulsar - Stack Overflow
I found the soulution. The original error was indeed caused by having an odd number of nodes. The third (virtual) one wouldn't start, ......
Read more >Troubleshooting Apache Pulsar Issues | Fusion 5.6
Clear Pulsar data · Execute the following command to obtain the number of existing replicas of statefulsets (STS) for both Pulsar Bookkeeper and...
Read more >Create an Apache Pulsar Cluster on Kubernetes - StreamNative
Manages the deployment of the Pulsar broker and Pulsar proxy for the ... You can find the three sets of Operators in the...
Read more >Quick Start for Helm Chart installs :: DataStax Luna Streaming
Via the provided DataStax Helm chart for an existing Kubernetes ... kubectl port-forward -n pulsar $(kubectl get pods -n pulsar -l component=broker -o ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This may be the solution…
If you are starting from fresh, you need to make sure to configure
PF_pulsarFunctionsCluster
correctly before deploying the worker.If you already started the worker with a wrong configuration, you can try this out:
And then redeploy the worker with a fixed configuration.
Would like to close this issue, since there was already a solution