itowey
04/24/2024, 11:11 PMfunctionsWorkerEnabled=true). Functions are deployed using the Process Runtime in the broker/Function Worker (FW) under a single container. (Note: This is a legacy deployment. Our plan is to upgrade to pulsar 3.0 and deploy the Function Worker as a set of standalone containers with Process Runtime, with the final step of moving to a Kubernetes StatefulSet and deploying functions on Kubernetes.)
The cluster had been running for an extended period without any downtime. However, after restarting the broker container, the Function Worker (along with all function endpoints) became unresponsive, with only about 10% of the expected functions restarting. Despite observing the Function Worker leadership reassigning after the broker container restart, it would not respond to any pulsar-admin commands.
Has anyone encountered a similar issue or has any suggestions on how to debug this situation?David K
04/25/2024, 2:20 PMitowey
04/25/2024, 3:56 PMDavid K
04/25/2024, 4:04 PMcurl <broker-ip>:8080/admin/v2/worker/cluster gives what output?itowey
04/25/2024, 7:04 PMworkerHostname is the advertisedAddress in broker.confitowey
04/25/2024, 7:06 PMadvertisedAddress does differ from the hostname of the VMDavid K
04/25/2024, 8:55 PMitowey
04/25/2024, 9:47 PMls /pulsar/functions/test/test/masked_func_name
we have 170 functions , why would only 1 have an entry in zk and not the others. Is this normal?David K
04/25/2024, 9:59 PMitowey
04/25/2024, 10:20 PM