OpenSearch Versions and Configurations
Versions
OpenSearch version 2.18 is supported. OpenSearch is distributed under the Apache 2.0 license.
Node group configurations
An OpenSearch Managed Database cluster consists of node groups. All nodes in a group have the same configuration — the number of vCPUs, RAM, and disk size. Configurations are divided into lines. The available lines depend on the node group role. Depending on the line, configuration, and pool, different processors and disks are used.
When choosing a configuration, keep in mind that part of the disk space is reserved for service needs and is unavailable for database placement. Learn more in the instruction Using disk space in an OpenSearch cluster.
The configuration can be selected when creating an OpenSearch Managed Database cluster. After the cluster is created, you can change the node group configuration — scale the node group.
Configuration lines
The resource ratio in configuration lines can be:
- fixed — in the Standard, CPU, Memory, and HighFreq (#highfreq-line) lines;
- or flexible — in the Flex line.
To check the availability of configuration lines across locations, see the instructions Cloud database availability by location.
Standard
The line is only available for node groups with Manager and Data roles — for details on roles, see the instructions Node groups.
A line of fixed configurations with a local disk and a balanced vCPU:RAM ratio, suitable for most DBMS. We recommend using this line if you do not know your load profile.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. You can view processor frequencies in different lines in the table Processors.
You can view disk performance and throughput in different lines in the table Performance and throughput.
CPU
The line is only available for node groups with Manager and Data roles — for details on roles, see the instructions Node groups.
A line of fixed configurations with a local disk and a balanced vCPU:RAM ratio. Suitable for workload profiles that are demanding on compute. For example, if the database performs analytical queries, multiple nested queries, or data encryption.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. You can view processor frequencies in different lines in the table Processors.
You can view disk performance and throughput in different lines in the table Performance and throughput.
Memory
The line is only available for node groups with Manager and Data roles — for details on roles, see the instructions Node groups.
A line of fixed configurations with a local disk and a balanced vCPU:RAM ratio. Suitable for workload profiles that are demanding on caching. For example, if multiple, rarely repeated queries to different parts of tables are executed in the database. One way to determine such a workload profile is to track the metric Попадание in кэш (Cache_hit_ratio), which shows the percentage of data in a query read from the cache.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. You can view processor frequencies in different lines in the table Processors.
You can view disk performance and throughput in different lines in the table Performance and throughput.
HighFreq
The line is only available for node groups with Manager and Data roles — for details on roles, see the instructions Node groups.
A line of fixed configurations with a balanced vCPU:RAM ratio.
High-performance Enterprise-level hardware is used:
- processors Intel® Xeon® Gold 6354 (in pools ru-9, ru-2, ru-8, ke-1) or AMD EPYC 9474F (in pools ru-3, ru-7, uz-1). You can view processor frequencies in different lines in the table Processors;
- RAM ECC Reg 3.2 GHz (in pools ru-9, ru-2, ru-8, ke-1) or RAM DDR5 ECC Reg 4.8 GHz (in pools ru-3, ru-7, uz-1);
- High-performance NVMe SSDs. You can view disk performance and throughput in different lines in the table Performance and throughput.
Flex
A line of custom configurations with a local or network volume, in which you can choose the resource ratio.
You can view disk information in the instructions Disks.
You can view disk performance and throughput in different lines in the table Performance and throughput.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. You can view processor frequencies in different lines in the table Processors.
Configuration limits depend on the pool.
Local disk
Network volume
* The vCPU:RAM ratio must be at least 1:2:
- for clusters in the ru-6 pool;
- for clusters in other pools, if the configuration has more than 8 vCPUs.
For example, for 10 vCPUs, you need at least 20 GB of RAM.
** The vCPU:Local disk ratio must be:
- at least 1:32 for clusters in the ru-1 pool, if the configuration has more than 8 vCPUs. For example, for 10 vCPUs, you need a volume of at least 320 GB;
- at least 1:16 for clusters in the ru-6 pool. For example, for 10 vCPUs, you need a volume of at least 160 GB;
- at least 1:16 for clusters in all pools except ru-1 and ru-6, if the configuration has more than 8 vCPUs.
If the configurations are not suitable, you can order a custom configuration. Create a ticket and specify the resource ratio.
Processors
Available processors vary by configuration lineup. Processor frequency affects the speed of processing user requests, executing complex algorithms, and performing data operations. When a cloud server is at 100% load, the processor uses Turbo Boost technology. Since the processor is emulated, the test will show a lower frequency.