why not stop external functions here? So what happens when the worker that the external function is assigned to dies? It seems with the current logic in the checkFailures method in MembershipManager, the external function will get reassigned and restarted. Is that what we want? You might also get a name conflict in kubernetes when the function gets restarted since the function already exists in kubernetes.
[ Full content available at: https://github.com/apache/pulsar/pull/1950 ] This message was relayed via gitbox.apache.org for [email protected]
