Skip to main content
Version: 2.0.0

HDD Storage With Data In Memory

This example lets you store namespace data both in memory and on the persistent device. For more information on setting up HDD storage with data-in-memory and other storage configurations, see the Aerospike documentation for namespace storage configuration.

To set this up, add the following storage-specific configuration to the Aerospike cluster's CR file.

  storage:
filesystemVolumePolicy:
cascadeDelete: false
initMethod: deleteFiles
volumes:
- name: workdir
aerospike:
path: /opt/aerospike
source:
persistentVolume:
storageClass: ssd
volumeMode: Filesystem
size: 1Gi
- name: ns
aerospike:
path: /opt/aerospike/data
source:
persistentVolume:
storageClass: ssd
volumeMode: Filesystem
size: 3Gi
- name: aerospike-config-secret
source:
secret:
secretName: aerospike-secret
aerospike:
path: /etc/aerospike/secret
.
.
.
aerospikeConfig:
service:
feature-key-file: /etc/aerospike/secret/features.conf
security: {}
namespace:
- name: test
memory-size: 3000000000
replication-factor: 2
storage-engine:
type: device
file:
- /opt/aerospike/data/test.dat
filesize: 2000000000
data-in-memory: true

For the full CR file, see the example HDD storage with data-in-memory cluster CR.

This and other example CRs are stored in the main Aerospike Kubernetes Operator repository.

Save and exit the CR file, then use kubectl to apply the change.

kubectl apply -f aerospike-cluster.yaml