The documentation you are viewing is for Dapr v1.10 which is an older version of Dapr. For up-to-date documentation, see the latest version.
Deprecation noticeThe Hazelcast PubSub component has been deprecated due to inherent lack of support for “at least once” delivery guarantee, and will be removed in a future Dapr release.
To setup hazelcast pubsub create a component of type
pubsub.hazelcast. See this guide on how to create and apply a pubsub configuration.
- name: hazelcastServers
WarningThe above example uses secrets as plain strings. It is recommended to use a secret store for the secrets as described here.
Spec metadata fields
|A comma delimited string of servers. Example: “hazelcast:3000,hazelcast2:3000”
|The maximum number of retries to process the message before returning an error. Defaults to
"0" which means the component will not retry processing the message.
"-1" will retry indefinitely until the message is processed or the application is shutdown. And positive number is treated as the maximum retry count. The component will wait 5 seconds between retries.
Create a Hazelcast instance
You can run Hazelcast locally using Docker:
docker run -e JAVA_OPTS="-Dhazelcast.local.publicAddress=127.0.0.1:5701" -p 5701:5701 hazelcast/hazelcast
You can then interact with the server using the
The easiest way to install Hazelcast on Kubernetes is by using the Helm chart.
- Basic schema for a Dapr component
- Read this guide for instructions on configuring pub/sub components
- Pub/Sub building block
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.