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. Available lines depend on the role of the node group. 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 system needs and is not available for hosting databases. Learn more in the Disk space usage in an OpenSearch cluster instructions.
You can select a configuration when creating an OpenSearch Managed Database cluster. After creating a cluster, 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 custom: in the Flex line.
You can check the availability of configuration lines across locations in the Managed Databases availability by location instructions.
Standard
The line is available only for node groups with Manager and Data roles. Learn more about roles in the Node groups instructions.
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 check the processor frequency in different lines in the Processors table.
You can check disk performance and bandwidth across different lines in the Performance and bandwidth table.
CPU
The line is available only for node groups with Manager and Data roles. Learn more about roles in the Node groups instructions.
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 check the processor frequency in different lines in the Processors table.
You can check disk performance and bandwidth across different lines in the Performance and bandwidth table.
Memory
The line is available only for node groups with Manager and Data roles. Learn more about roles in the Node groups instructions.
A line of fixed configurations with a local disk and a balanced vCPU:RAM ratio. Suitable for cache-sensitive workload profiles. For example, if multiple, rarely repeating queries to different parts of tables are executed in the database. One way to identify such a workload profile is to monitor the Cache hit (Cache_hit_ratio) metric, which shows the percentage of data in a query read from the cache.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. You can check the processor frequency in different lines in the Processors table.
You can check disk performance and bandwidth across different lines in the Performance and bandwidth table.
HighFreq
The line is available only for node groups with Manager and Data roles. Learn more about roles in the Node groups instructions.
A line of fixed configurations with a balanced vCPU:RAM ratio.
High-performance Enterprise-level hardware is used:
- Intel® Xeon® Gold 6354 processors (in pools ru-9, ru-2, ru-8, ke-1) or AMD EPYC 9474F (in pools ru-3, ru-7, uz-1). You can check the processor frequency in different lines in the Processors table;
- 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 check disk performance and bandwidth across different lines in the Performance and bandwidth table.
Flex
A line of custom configurations with a local or network volume, in which you can choose the resource ratio.
You can check disk information in the Disks instructions.
You can check disk performance and bandwidth across different lines in the Performance and bandwidth table.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. You can check the processor frequency in different lines in the Processors table.
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 do not suit your needs, 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.