Valkey™ version upgrade
You can upgrade a Yandex Managed Service for Valkey™ cluster to any supported version.
Supported versions
All Valkey™ versions supported in Yandex Managed Service for Valkey™ remain available as long as they are supported by the vendor. Typically, this is 24 months from the version release date. For more information, see this Valkey™ guide
Viewing a list of available Valkey™ versions
- Navigate to the Yandex Managed Service for Valkey™ service.
- Select the cluster and click Edit.
- Open the list in the Version field.
Note
To specify a version number in the CLI, Terraform, and the API, add the -valkey suffix to it, e.g., 8.1-valkey.
Before upgrading a version
Make sure the upgrade will not disrupt your applications:
- Check the Valkey™ release notes
to learn how upgrades may affect your applications. - Try upgrading a test cluster. You can deploy it from a backup of the main cluster, if Yandex Managed Service for Valkey™ supports the Valkey™ version in the backup.
- Create a backup of the main cluster immediately before upgrading.
Upgrading a cluster
Alert
- After the DBMS upgrade, you cannot revert the cluster to the previous version.
- Whether a Valkey™ version upgrade succeeds depends on multiple factors, including your cluster’s configuration and the nature of the stored data. We recommend that you start with upgrading a test cluster with the same data and configuration.
- In the management console
, go to the folder containing the cluster to upgrade. - Navigate to the Yandex Managed Service for Valkey™ service.
- Select the cluster you need from the list and click Edit.
- In the Version field, select the new version.
- Click Save changes.
As soon as you run the upgrade, the cluster status will change to Updating. Wait for the operation to complete and then check the cluster version.
If you do not have the Yandex Cloud CLI installed yet, install and initialize it.
By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.
-
Get the list of your Valkey™ clusters using this command:
yc managed-redis cluster list -
Get information about the cluster in question and check its Valkey™ version in the
config.versionsetting:yc managed-redis cluster get <cluster_name_or_ID> -
Start the Valkey™ upgrade:
yc managed-redis cluster update <cluster_name_or_ID> \ --redis-version <new_version_number>As soon as you run the upgrade, the cluster status will change to Updating. Wait for the operation to complete and then check the cluster version.
-
Open the current Terraform configuration file describing your infrastructure.
To learn how to create this file, see Creating a cluster.
-
Update the
versionargument in theconfigsection to specify the Valkey™ version you want to upgrade to:resource "yandex_mdb_redis_cluster_v2" "<cluster_name>" { ... config { version = "<new_version_number>" ... } } -
Validate your configuration.
-
In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.
-
Run this command:
terraform validateTerraform will show any errors found in your configuration files.
-
-
Confirm updating the resources.
-
Run this command to view the planned changes:
terraform planIf you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.
-
If everything looks correct, apply the changes:
-
Run this command:
terraform apply -
Confirm updating the resources.
-
Wait for the operation to complete.
-
-
For more information, see this Terraform provider guide.
Timeouts
The Terraform provider sets the following timeouts for Yandex Managed Service for Valkey™ cluster operations:
- Creating a cluster, including by restoring it from a backup: 15 minutes.
- Editing a cluster: 60 minutes.
- Deleting a cluster: 15 minutes.
Operations exceeding the timeout are aborted.
How do I change these limits?
Add the timeouts section to your cluster description, such as the following:
resource "yandex_mdb_redis_cluster_v2" "<cluster_name>" {
...
timeouts {
create = "1h30m" # 1 hour 30 minutes
update = "2h" # 2 hours
delete = "30m" # 30 minutes
}
}
-
Get an IAM token for API authentication and place it in an environment variable:
export IAM_TOKEN="<IAM_token>" -
Use the Cluster.Update method and send the following request, e.g., via cURL
:Warning
The API method will assign default values to all the parameters of the object you are modifying unless you explicitly provide them in your request. To avoid this, list the settings you want to change in the
updateMaskparameter as a single comma-separated string.curl \ --request PATCH \ --header "Authorization: Bearer $IAM_TOKEN" \ --header "Content-Type: application/json" \ --url 'https://mdb.api.cloud.yandex.net/managed-redis/v1/clusters/<cluster_ID>' \ --data '{ "updateMask": "configSpec.version", "configSpec": { "version": "<Valkey™_version>" } }'Where:
-
updateMask: Comma-separated string of settings you want to update.Here, we provide only one setting.
-
configSpec.version: New Valkey™ version.
You can request the cluster ID with the list of clusters in the folder.
-
-
Check the server response to make sure your request was successful.
-
Get an IAM token for API authentication and place it in an environment variable:
export IAM_TOKEN="<IAM_token>" -
Clone the cloudapi
repository:cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapiBelow, we assume that the repository contents reside in the
~/cloudapi/directory. -
Call the ClusterService.Update method, e.g., via the following gRPCurl
request:Warning
The API method will assign default values to all the parameters of the object you are modifying unless you explicitly provide them in your request. To avoid this, list the settings you want to change in the
update_maskparameter as an array ofpaths[]strings.Format for listing settings
"update_mask": { "paths": [ "<setting_1>", "<setting_2>", ... "<setting_N>" ] }grpcurl \ -format json \ -import-path ~/cloudapi/ \ -import-path ~/cloudapi/third_party/googleapis/ \ -proto ~/cloudapi/yandex/cloud/mdb/redis/v1/cluster_service.proto \ -rpc-header "Authorization: Bearer $IAM_TOKEN" \ -d '{ "cluster_id": "<cluster_ID>", "update_mask": { "paths": [ "config_spec.version" ] }, "config_spec": { "version": "<Valkey™_version>" } }' \ mdb.api.cloud.yandex.net:443 \ yandex.cloud.mdb.redis.v1.ClusterService.UpdateWhere:
-
update_mask: List of parameters to update as an array of strings (paths[]).Here, we provide only one setting.
-
config_spec.version: New Valkey™ version.
You can request the cluster ID with the list of clusters in the folder.
-
-
Check the server response to make sure your request was successful.
Examples
Let's assume you need to upgrade your cluster version from 8.1 to 9.0.
-
To get the list of clusters with their IDs and names, run this command:
yc managed-redis cluster listResult:
+----------------------+---------------+---------------------+--------+---------+ | ID | NAME | CREATED AT | HEALTH | STATUS | +----------------------+---------------+---------------------+--------+---------+ | c9q8p8j2gaih******** | redis406 | 2022-04-23 12:44:17 | ALIVE | RUNNING | +----------------------+---------------+---------------------+--------+---------+ -
To get information about the
redis406cluster, run the following command:yc managed-redis cluster get redis406Result:
id: c9q8p8j2gaih******** ... config: version: 8.1-valkey ... -
To upgrade a cluster named
redis406to version9.0, run the following command:yc managed-redis cluster update redis406 --redis-version 9.0-valkey`