Hazelcast
Detailed documentation on the Hazelcast pubsub component
Component format
To setup hazelcast pubsub create a component of type pubsub.hazelcast. See this guide on how to create and apply a pubsub configuration.
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: hazelcast-pubsub
namespace: default
spec:
type: pubsub.hazelcast
version: v1
metadata:
- name: hazelcastServers
value: "hazelcast:3000,hazelcast2:3000"
Warning
The above example uses secrets as plain strings. It is recommended to use a secret store for the secrets as described here.Spec metadata fields
| Field | Required | Details | Example |
|---|---|---|---|
| connectionString | Y | A comma delimited string of servers. Example: “hazelcast:3000,hazelcast2:3000” | "hazelcast:3000,hazelcast2:3000" |
| backOffMaxRetries | N | 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. | "3" |
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 127.0.0.1:5701.
The easiest way to install Hazelcast on Kubernetes is by using the Helm chart.
Related links
- Basic schema for a Dapr component
- Read this guide for instructions on configuring pub/sub components
- Pub/Sub building block
Last modified May 22, 2021: docs: clean up white noise (#1491) (fe1ab8eb)