Hazelcast

Detailed documentation on the Hazelcast pubsub component

Deprecation notice

The 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.

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.

  1. apiVersion: dapr.io/v1alpha1
  2. kind: Component
  3. metadata:
  4.   name: hazelcast-pubsub
  5. spec:
  6.   type: pubsub.hazelcast
  7.   version: v1
  8.   metadata:
  9.   - name: hazelcastServers
  10.     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

FieldRequiredDetailsExample
connectionStringYA comma delimited string of servers. Example: “hazelcast:3000,hazelcast2:3000”“hazelcast:3000,hazelcast2:3000”
backOffMaxRetriesNThe 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:

  1. 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.

Last modified December 21, 2022: Docs upmerge 12/16 (#3015) (268da740)