Set up function workers

You have two ways to set up function workers.

• Run function workers with brokers. Use it when:
  • resource isolation is not required when running functions in process or thread mode;
  • you configure the function workers to run functions on Kubernetes (where the resource isolation problem is addressed by Kubernetes).
• Run function workers separately. Use it when you want to separate functions and brokers.

Optional configurations

• Configure temporary file path
• Enable stateful functions
• Configure function workers for geo-replicated clusters

Reference

• Troubleshooting

Custom worker extensions

Pulsar generates the Java messages in org.apache.pulsar.functions.proto with LightProto. Custom worker authentication providers, schedulers, runtimes, or other extensions that use these types must compile against the worker's API. For example, FunctionAuthProvider methods accept the top-level FunctionDetails type. Generated messages use mutable instances and setters. For migration from older generated APIs, see the upgrade guide.

Ordinary function code should use the public Functions SDK rather than generated worker message types.