This is a prerelease version.

View latest

Tiered Storage

latest-snapshot 5.14 5.13 5.12 5.11 5.10 5.9 5.8 5.7 5.6 5.5

Tiered Storage offers an extension to Hazelcast map, which allows you to store a larger data set than the available memory can accommodate.

For further information on the configuration and behavior of Tiered Storage in Hazelcast, refer to Tiered Storage in the Platform documentation.

The configuration of Tiered Storage includes setting the local device (local disk) parameters for the Hazelcast CR and providing Tiered Storage details for the Map CR.

Configuring Local Devices

You must enable the native memory to use Tiered Storage; see Native Memory to learn how to enable it.

Before configuring the native memory and local devices, see Tiered Storage Capacity Planning for tips on sizing the memory and disk tiers.

You can configure one or more local devices in a single Hazelcast CR. A separate PersistentVolumeClaim (PVC) is created for each local device and used as the local disk for that device. Therefore, the number of created PVCs matches the cluster size for each configured local device.

For example, if you create two local devices (device1 , device2) for a Hazelcast CR called hazelcast, and the size of your cluster is 3, a total of six PVCs are created as follows:

  • device1-hazelcast-0

  • device1-hazelcast-1

  • device1-hazelcast-2

  • device2-hazelcast-0

  • device2-hazelcast-1

  • device2-hazelcast-2

Example of a Hazelcast CR
apiVersion: hazelcast.com/v1alpha1
kind: Hazelcast
metadata:
  name: hazelcast-sample
spec:
  clusterSize: 3
  repository: 'docker.io/hazelcast/hazelcast-enterprise'
  licenseKeySecretName: hazelcast-license-key
  localDevices:
    - name: device-sample
      blockSize: 4096
      readIOThreadCount: 4
      writeIOThreadCount: 4
      pvc:
        accessModes: ["ReadWriteOnce"]
        requestStorage: 8Gi
  nativeMemory:
    size: 1280M

Configuring a Map with Tiered Storage

In-memory format must be NATIVE for the maps with Tiered Storage.

Example of a Map CR with Tiered Storage
apiVersion: hazelcast.com/v1alpha1
kind: Map
metadata:
  name: map-sample
spec:
  hazelcastResourceName: hazelcast-sample
  inMemoryFormat: NATIVE
  tieredStore:
    memoryCapacity: 128M
    diskDeviceName: device-sample

Configuration-based Validation

  • Native memory must be enabled on the Hazelcast CR. Basically, when you set a size for the native memory, it means it is enabled; see the example Hazelcast CR in Configuring Local Devices.

  • The inMemoryFormat option must be NATIVE on the Map CR. See the example Map CR in Configuring a Map with Tiered Storage.

  • Data Persistence and Tiered Storage are mutually exclusive features; you cannot enable both simultaneously in the Map configuration. The persistenceEnabled option on the Map CR must be false, which is the default value, when using Tiered Storage.

  • Indexes, eviction, and time-to-live and max-idle expirations are not supported for the maps with Tiered Storage.

  • Configured local device size on the Hazelcast CR (LocalDevice.PVC.RequestStorage) must be higher than MemoryCapacity on the Map CR.

  • Native Memory size (NativeMemory.Size) on the Hazelcast CR must be higher than the sum of memory capacities (TieredStore.MemoryCapacity) on all Map CRs.

lifebuoy

Help and support