OpenSearch versions and configurations
Versions
OpenSearch version 2.18 is supported. OpenSearch is distributed via Apache 2.0 licenses.
Node group configurations
The OpenSearch cloud database cluster consists of node groups. All nodes in the group have the same configuration — number of vCPUs, RAM and disk size. The configurations are divided into rulers. The available rulers and ruler configurations depend on the role of the node group.
When selecting a configuration, consider that about 5 GB of disk space in all configurations is reserved for the operating system, service components, and log storage. The rest of the disk space is available for databases.
The configuration can be selected by creation of the OpenSearch cloud database cluster. Once the cluster is created, you can change the configuration of the node group — scale the node group.
Configuration lines
The available node configurations are divided into rulers. The selected line of configurations depends on the configurations used disks.
The ratio of resources in line configurations can be:
To see the availability of the configuration lines in the regions, see the availability matrix Cloud databases.
Standard
The ruler is available only for node groups with Manager and Data roles — more details about the roles in the manual Groups of nodes.
A line of fixed configurations with local disk and balanced vCPU:RAM ratio, suitable for most DBMSs. We recommend using this lineup if you do not know the load profile.
Intel® Xeon® Scalable or AMD EPYC™ 2.2-2.4 GHz processors are used.
To see the performance and throughput of the drives in the different lines, see the table below Performance and throughput.
CPU
The ruler is available only for node groups with Manager and Data roles — more details about the roles in the manual Groups of nodes.
A line of fixed configurations with local disk and balanced vCPU:RAM ratio. Suitable for workload profiles that are computationally demanding. For example, if the database is running analytic queries, multiple nested queries, or data encryption. One way to determine such a load profile is to track metrics Load Averagewhich shows the average system utilization over one, five or 15 minutes.
Intel® Xeon® Scalable or AMD EPYC™ 2.2-2.4 GHz processors are used.
To see the performance and throughput of the drives in the different lines, see the table below Performance and throughput.
Memory
The ruler is available only for node groups with Manager and Data roles — more details about the roles in the manual Groups of nodes.
A line of fixed configurations with local disk and balanced vCPU:RAM ratio. Suitable for workload profiles that are cache-intensive. For example, if the database runs multiple, infrequent queries on different parts of tables. One way to determine such a load profile is to monitor the metric Попадание в кэш (Cash_hit_ratio)which shows the percentage of data in the query that is read from the cache.
Intel® Xeon® Scalable or AMD EPYC™ 2.2-2.4 GHz processors are used.
To see the performance and throughput of the drives in the different lines, see the table below Performance and throughput.
Flex
A lineup of custom configurations with local disk, in which you can choose the resource ratio.
To see the performance and throughput of the drives in the different lines, see the table below Performance and throughput.
Intel® Xeon® Scalable or AMD EPYC™ 2.2-2.4 GHz processors are used.
Configuration limits depend on pool. To see the availability of configurations in the regions, see the availability matrix Cloud databases.
* If there are more than 8 vCPUs in a configuration, the vCPU:RAM ratio must be at least 1:4. For example, 10 vCPUs require at least 40 GB of RAM.
** If the configuration has more than 8 vCPUs, the vCPU:Local Disk ratio must be at least 1:32. For example, 10 vCPUs require a disk size of at least 320 GB.
If the configurations are not suitable, you can order your own configuration. Create a ticket and indicate the ratio of resources:
- vCPU:RAM — at least 1:4;
- vCPU:RAM:Local disk — at least 1:4:32.
SDS
A line of random configurations with a network disk in which you can select the resource ratio. The network disk is managed by Software-Defined Storage (SDS) — Ceph. Ceph provides three-fold replication of disk volumes.
Network latency with network disks is higher than with local disks, so it is not recommended to use the SDS line for systems sensitive to network latency and latency. Suitable for archival storage.
When changing disk size in SDS line configurations, there is no down time regardless of the number of nodes in the cluster. When changing the number of vCPUs and RAM, the down time depends on the number of nodes in the cluster: in single-node clusters, the down time is equal to the time to reboot a node (one to two minutes), and in multi-node clusters, the down time is equal to the time to switch to another node (less than one minute).
To see the performance and throughput of the drives in the different lines, see the table below Performance and throughput.
Intel® Xeon® Scalable or AMD EPYC™ 2.2-2.4 GHz processors are used.
Configuration limits depend on pool. To see the availability of configurations in the regions, see the availability matrix Cloud databases.