Hazelcast
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>
namespace: <NAMESPACE>
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.
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 |
---|---|---|---|
hazelcastServers | Y | A comma delimited string of servers | “hazelcast:3000,hazelcast2:3000” |
hazelcastMap | Y | Hazelcast Map configuration | “foo-map” |
Setup Hazelcast
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 state store components
- State management building block
Last modified March 18, 2021: Merge pull request #1321 from dapr/aacrawfi/logos (9a399d5)