The documentation you are viewing is for Dapr v1.9 which is an older version of Dapr. For up-to-date documentation, see the latest version.
Detailed information on the Hazelcast state store component
Create a Dapr component
To setup Hazelcast state store create a component of type
state.hazelcast. See this guide on how to create and apply a state store configuration.
apiVersion: dapr.io/v1alpha1 kind: Component metadata: name: <NAME> spec: type: state.hazelcast version: v1 metadata: - name: hazelcastServers value: <REPLACE-WITH-HOSTS> # Required. A comma delimited string of servers. Example: "hazelcast:3000,hazelcast2:3000" - name: hazelcastMap value: <REPLACE-WITH-MAP> # Required. Hazelcast map configuration.
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
|hazelcastServers||Y||A comma delimited string of servers||
|hazelcastMap||Y||Hazelcast Map configuration||
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 state store components
- State management 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.
Last modified July 27, 2022: Remove namespace element from component examples (#2647) (ff9de5c8)