Oneeb
02/19/2024, 10:25 AMHTTP 503 Service Unavailable error. I then have to manually restart the function. As I understand it, this is because when the broker restarts, it creates the functions but the function worker service is not up at the time and so the function creation fails with the 503 error. Am I missing something wrt to I how I’ve configured my functions or function worker? The only function worker config I have changed is that I use the ThreadRuntime. Would love some input on how I can ensure the function starts up properly and doesn’t require manual intervention.
Attaching logs here for the stack trace.
Thanks!Oneeb
02/19/2024, 7:17 PMMing
02/19/2024, 7:41 PMfunctionRuntimeFactoryClassName: org.apache.pulsar.functions.runtime.thread.ThreadRuntimeFactory in functions_worker.yaml
it looks like your function worker is not configured properly. Maybe test which function endpoints work that can give some clue where is broken.Oneeb
02/20/2024, 11:41 AMOneeb
02/20/2024, 11:41 AMOneeb
02/20/2024, 12:54 PMbroker.conf functionsWorkerEnablePackageManagement=true but in the functions_worker.yml its set to false functionsWorkerEnablePackageManagement: false
Could the difference be the reason this is happening? And since Im trying to use the official apache/pulsar helm chart is there a way to set this through that?Oneeb
02/21/2024, 1:28 PMAsaf Mesika
02/21/2024, 1:38 PMNeng
02/21/2024, 5:49 PMfunctionsWorkerEnablePackageManagement is for uploading function/connector jars with the pulsar-admin packages ... cmd.Neng
02/21/2024, 5:49 PMNeng
02/21/2024, 5:50 PMOneeb
02/21/2024, 5:53 PMOneeb
02/21/2024, 5:53 PMOneeb
02/21/2024, 5:54 PM