Questions and answers about Managed Service for Elasticsearch
Warning
Yandex Managed Service for Elasticsearch is unavailable as of April 11, 2024.
You can create an OpenSearch cluster in Yandex Cloud as an alternative to Elasticsearch.
-
Which Elasticsearch version does Managed Service for Elasticsearch use?
-
What happens when an Elasticsearch version becomes deprecated?
-
Why is the cluster slow even though the computing resources are not used fully?
General questions
How are Elasticsearch clusters maintained?
Maintenance in Managed Service for Elasticsearch implies:
- Automatic installation of Elasticsearch updates and fixes for your database hosts.
- Changes to the host class and storage size.
- Other Managed Service for Elasticsearch maintenance activities.
For more information, see Maintenance.
Is cluster backup enabled by default?
Yes, backup is enabled by default. For Managed Service for Elasticsearch clusters, a full backup takes place once per hour and saves all indexes. This helps restore a cluster's state from any available backup.
Backups are kept for seven days.
Which Elasticsearch version does Managed Service for Elasticsearch use?
The Elasticsearch versions maintained by the vendor are available in Managed Service for Elasticsearch. For more information, see Elasticsearch versioning policy.
What happens when a new Elasticsearch version is released?
When new versions include only bug fixes (such versions are called maintenance releases), the cluster software is automatically updated after a short testing period.
Owners of the affected DB clusters are notified of expected work times and DB availability in advance.
What happens when an Elasticsearch version becomes deprecated?
Managed Service for Elasticsearch automatically notifies cluster owners by email that their Elasticsearch version is approaching end of life.
Clusters running a deprecated version of Elasticsearch are updated according to the version control policy.
Owners of the affected clusters are notified of expected work times and DB availability in advance.
Can I get logs of my operations with services?
Yes, you can request log records about your resources from Yandex Cloud services. For more information, see Data requests.
What is the retention period for logs?
Cluster logs are stored for 30 days.
How do I set up an alert that triggers as soon as a certain percentage of disk space has been used up?
Create an alert with the disk.used_bytes
metric in Yandex Monitoring. This metric shows the disk space usage in the Managed Service for Elasticsearch cluster.
For disk.used_bytes
, use notification thresholds. The recommended values are as follows:
Alarm
: 90% of the disk spaceWarning
: 80% of the disk space
Thresholds are set in bytes only. For example, the recommended values for a 100 GB disk are as follows:
Alarm
:96,636,764,160
bytes (90%)Warning
:85,899,345,920
bytes (80%)
Why is the cluster slow even though the computing resources are not used fully?
Perhaps, the maximum storage IOPS and bandwidth values are insufficient for processing the current number of requests. In this case, throttling is triggered and the performance of the entire cluster degrades.
The maximum IOPS and bandwidth values increase by a fixed value when the storage size increases by a certain step. The step and increment values depend on the disk type:
Disk type | Step, GB | Max IOPS increase (read/write) | Max bandwidth increase (read/write), MB/s |
---|---|---|---|
network-hdd |
256 | 300/300 | 30/30 |
network-ssd |
32 | 1,000/1,000 | 15/15 |
network-ssd-nonreplicated |
93 | 28,000/5,600 | 110/82 |
To increase the maximum IOPS and bandwidth values and make throttling less likely, increase the storage size when you update your cluster.
If you are using the network-hdd
storage type, consider switching to network-ssd
or network-ssd-nonreplicated
by restoring the cluster from a backup.