Skip to main content

Volumes in an OpenSearch cluster

In an OpenSearch Managed Database cluster, you can use local and network volumes. The disk type used depends on the selected configuration line.

You can select a configuration line with the required disk type and disk size when creating a Managed Database cluster. After the cluster is created, you can change the line to another one with the same disk type and increase the disk size — scale the cluster.

Performance and throughput for disks in various configuration lines can be viewed in the Performance and throughput table.

Local disks

Configuration lines
  • Standard;
  • CPU;
  • Memory;
  • Flex
Disk typeSSD NVMe disk
Technical details The disk subsystem is configured in RAID 10 for the Standard, CPU, Memory, HighFreq, and Flex lines
BenefitsLow data access latency
UsageSuitable for tasks sensitive to read and write speed metrics
Number of disks in DBMS1
Configuration change
  • in all configuration lines with a local disk, except for Flex, you cannot increase the local disk only; you must change the entire node configuration — scale the cluster;
Disconnecting a disk✗
Connecting to another database✗
Creating another disk, snapshot, or backup✗
DeletionDeleted along with all data when the cluster is deleted

Network volumes

Configuration linesFlex
Disk typeSSD NVMe disk
Technical detailsManaged by a Software-Defined Storage (SDS) system — Ceph
Benefits
  • triple replication of disk volumes;
  • network volume size is independent of the number of vCPUs
UsageNot recommended for latency-sensitive systems. For example, it is suitable for archive data storage. ( )
Number of disks in DBMS1
Configuration change
  • no downtime when changing disk size;
  • when changing the number of vCPU and RAM, the downtime depends on the number of nodes in the cluster: in single-node clusters, downtime is equal to the node restart time (one to two minutes), and in multi-node clusters, it is equal to the time required to switch to another node (less than one minute)
Detaching a volume✗
Connecting to another database✗
Creating another volume, snapshot, or backup✗
DeletionDeleted along with all data when the cluster is deleted

Performance and throughput

Throughput400 MB/s
Performance (read)25 600 IOPS
Performance (write)12 800 IOPS