lhotari commented on PR #23829: URL: https://github.com/apache/pulsar/pull/23829#issuecomment-2581309688
> The function worker does not recover, leading to an ongoing failure. With this update, the worker will automatically restart with the help of health check with liveliness probe upon encountering this error, ensuring proper recovery and continuity of operations. Although adding a liveness check could be useful for many reasons, it would be better to primarily address this issue. Are you able to isolate and reproduce the issue? What Pulsar version are you running? It looks like the leader election for the function worker uses a consumer with `consumerEventListener` to find who is the leader: https://github.com/apache/pulsar/blob/3396065a3a62af3e3586700f0bbfcbff93716b48/pulsar-functions/worker/src/main/java/org/apache/pulsar/functions/worker/LeaderService.java#L76-L87 There might be a bug in the Pulsar implementation of notifying the active consumer change: https://github.com/apache/pulsar/blob/49aa3080d422994baa036ed0b743a2fa18a6d530/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/AbstractDispatcherSingleActiveConsumer.java#L213-L223 At least by reading the code, it's hard to see how that could work. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
