From 4d1d8272a5a9d19d275c4a1017f7faf0e10609d9 Mon Sep 17 00:00:00 2001 From: Milvus-doc-bot Date: Thu, 17 Oct 2024 09:23:26 +0000 Subject: [PATCH] Release new docs --- v2.4.x/Variables.json | 4 +-- v2.4.x/site/en/adminGuide/configure-docker.md | 8 +++--- v2.4.x/site/en/adminGuide/operator.md | 2 +- .../upgrade_milvus_cluster-docker.md | 20 ++++++------- .../adminGuide/upgrade_milvus_cluster-helm.md | 28 +++++++++---------- .../upgrade_milvus_cluster-operator.md | 20 ++++++------- .../upgrade_milvus_standalone-docker.md | 6 ++-- .../upgrade_milvus_standalone-helm.md | 28 +++++++++---------- .../upgrade_milvus_standalone-operator.md | 20 ++++++------- .../install_standalone-docker-compose.md | 2 +- .../install_standalone-docker-compose-gpu.md | 4 +-- v2.4.x/site/en/release_notes.md | 16 ++++++++++- 12 files changed, 86 insertions(+), 72 deletions(-) diff --git a/v2.4.x/Variables.json b/v2.4.x/Variables.json index df90b07e8..761803d82 100644 --- a/v2.4.x/Variables.json +++ b/v2.4.x/Variables.json @@ -1,6 +1,6 @@ { - "milvus_release_version": "2.4.13", - "milvus_release_tag": "2.4.13", + "milvus_release_version": "2.4.13-hotfix", + "milvus_release_tag": "2.4.13-hotfix", "milvus_deb_name": "milvus_2.2.0-1_amd64", "milvus_rpm_name": "milvus-2.2.0-1.el7.x86_64", "milvus_python_sdk_version": "2.4.x", diff --git a/v2.4.x/site/en/adminGuide/configure-docker.md b/v2.4.x/site/en/adminGuide/configure-docker.md index 1f890b3e3..23af3daa3 100644 --- a/v2.4.x/site/en/adminGuide/configure-docker.md +++ b/v2.4.x/site/en/adminGuide/configure-docker.md @@ -16,10 +16,10 @@ In current release, all parameters take effect only after Milvus restarts. ## Download a configuration file -[Download](https://raw.githubusercontent.com/milvus-io/milvus/v2.4.13/configs/milvus.yaml) `milvus.yaml` directly or with the following command. +[Download](https://raw.githubusercontent.com/milvus-io/milvus/v2.4.13-hotfix/configs/milvus.yaml) `milvus.yaml` directly or with the following command. ``` -$ wget https://raw.githubusercontent.com/milvus-io/milvus/v2.4.13/configs/milvus.yaml +$ wget https://raw.githubusercontent.com/milvus-io/milvus/v2.4.13-hotfix/configs/milvus.yaml ``` ## Modify the configuration file @@ -178,13 +178,13 @@ Sorted by: ## Download an installation file -Download the installation file for Milvus [standalone](https://github.com/milvus-io/milvus/releases/download/v2.4.13/milvus-standalone-docker-compose.yml), and save it as `docker-compose.yml`. +Download the installation file for Milvus [standalone](https://github.com/milvus-io/milvus/releases/download/v2.4.13-hotfix/milvus-standalone-docker-compose.yml), and save it as `docker-compose.yml`. You can also simply run the following command. ``` # For Milvus standalone -$ wget https://github.com/milvus-io/milvus/releases/download/v2.4.13/milvus-standalone-docker-compose.yml -O docker-compose.yml +$ wget https://github.com/milvus-io/milvus/releases/download/v2.4.13-hotfix/milvus-standalone-docker-compose.yml -O docker-compose.yml ``` ## Modify the installation file diff --git a/v2.4.x/site/en/adminGuide/operator.md b/v2.4.x/site/en/adminGuide/operator.md index bd90e06e4..84b821443 100644 --- a/v2.4.x/site/en/adminGuide/operator.md +++ b/v2.4.x/site/en/adminGuide/operator.md @@ -12,7 +12,7 @@ Milvus cluster depends on components including object storage, etcd, and Pulsar. This topic assumes that you have deployed Milvus Operator. -
See Deploy Milvus Operator for more information.
+
See Deploy Milvus Operator for more information.
You need to specify a configuration file for using Milvus Operator to start a Milvus cluster. diff --git a/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-docker.md b/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-docker.md index cfb5f4422..89b0266c2 100644 --- a/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-docker.md +++ b/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-docker.md @@ -10,7 +10,7 @@ title: Upgrade Milvus Cluster with Docker Compose This topic describes how to upgrade your Milvus using Docker Compose. -In normal cases, you can [upgrade Milvus by changing its image](#Upgrade-Milvus-by-changing-its-image). However, you need to [migrate the metadata](#Migrate-the-metadata) before any upgrade from v2.1.x to v2.4.13. +In normal cases, you can [upgrade Milvus by changing its image](#Upgrade-Milvus-by-changing-its-image). However, you need to [migrate the metadata](#Migrate-the-metadata) before any upgrade from v2.1.x to v2.4.13-hotfix. ## Upgrade Milvus by changing its image @@ -24,35 +24,35 @@ In normal cases, you can upgrade Milvus as follows: ... rootcoord: container_name: milvus-rootcoord - image: milvusdb/milvus:v2.4.13 + image: milvusdb/milvus:v2.4.13-hotfix ... proxy: container_name: milvus-proxy - image: milvusdb/milvus:v2.4.13 + image: milvusdb/milvus:v2.4.13-hotfix ... querycoord: container_name: milvus-querycoord - image: milvusdb/milvus:v2.4.13 + image: milvusdb/milvus:v2.4.13-hotfix ... querynode: container_name: milvus-querynode - image: milvusdb/milvus:v2.4.13 + image: milvusdb/milvus:v2.4.13-hotfix ... indexcoord: container_name: milvus-indexcoord - image: milvusdb/milvus:v2.4.13 + image: milvusdb/milvus:v2.4.13-hotfix ... indexnode: container_name: milvus-indexnode - image: milvusdb/milvus:v2.4.13 + image: milvusdb/milvus:v2.4.13-hotfix ... datacoord: container_name: milvus-datacoord - image: milvusdb/milvus:v2.4.13 + image: milvusdb/milvus:v2.4.13-hotfix ... datanode: container_name: milvus-datanode - image: milvusdb/milvus:v2.4.13 + image: milvusdb/milvus:v2.4.13-hotfix ``` 2. Run the following commands to perform the upgrade. @@ -80,7 +80,7 @@ In normal cases, you can upgrade Milvus as follows: runWithBackup: true config: sourceVersion: 2.1.4 # Specify your milvus version - targetVersion: 2.4.13 + targetVersion: 2.4.13-hotfix backupFilePath: /tmp/migration.bak metastore: type: etcd diff --git a/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md b/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md index 260bbac00..1d2c61e03 100644 --- a/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md +++ b/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md @@ -75,11 +75,11 @@ zilliztech/milvus 4.1.0 2.3.0 Milvus is an ope You can choose the upgrade path for your Milvus as follows: -
- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.4.13.
+
- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.4.13-hotfix.
-- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.4.13. +- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.4.13-hotfix. -- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.4.13. +- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.4.13-hotfix.
@@ -101,10 +101,10 @@ The script applies only to the upgrade of Milvus installed with Helm. The follow | `w` | New Milvus image tag | `milvusdb/milvus:v2.2.3` | True | | `o` | Operation | `update` | False | -Once you have ensured that all deployments in your Milvus instance are in their normal status. You can run the following command to upgrade the Milvus instance to 2.4.13. +Once you have ensured that all deployments in your Milvus instance are in their normal status. You can run the following command to upgrade the Milvus instance to 2.4.13-hotfix. ```shell -sh rollingUpdate.sh -n default -i my-release -o update -t 2.4.13 -w 'milvusdb/milvus:v2.4.13' +sh rollingUpdate.sh -n default -i my-release -o update -t 2.4.13-hotfix -w 'milvusdb/milvus:v2.4.13-hotfix' ```
@@ -214,43 +214,43 @@ The following table lists the operations you can do for meta migration. 4. Migrate the Milvus metadata. 5. Start Milvus components with a new image. -#### 2. Upgrade Milvus from v2.1.x to 2.4.13 +#### 2. Upgrade Milvus from v2.1.x to 2.4.13-hotfix -The following commands assume that you upgrade Milvus from v2.1.4 to 2.4.13. Change them to the versions that fit your needs. +The following commands assume that you upgrade Milvus from v2.1.4 to 2.4.13-hotfix. Change them to the versions that fit your needs. 1. Specify Milvus instance name, source Milvus version, and target Milvus version. ``` - ./migrate.sh -i my-release -s 2.1.4 -t 2.4.13 + ./migrate.sh -i my-release -s 2.1.4 -t 2.4.13-hotfix ``` 2. Specify the namespace with `-n` if your Milvus is not installed in the default K8s namespace. ``` - ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13 + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13-hotfix ``` 3. Specify the root path with `-r` if your Milvus is installed with the custom `rootpath`. ``` - ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13 -r by-dev + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13-hotfix -r by-dev ``` 4. Specify the image tag with `-w` if your Milvus is installed with a custom `image`. ``` - ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13 -r by-dev -w milvusdb/milvus:v2.4.13 + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13-hotfix -r by-dev -w milvusdb/milvus:v2.4.13-hotfix ``` 5. Set `-d true` if you want to automatically remove the migration pod after the migration is completed. ``` - ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13 -w milvusdb/milvus:v2.4.13 -d true + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13-hotfix -w milvusdb/milvus:v2.4.13-hotfix -d true ``` 6. Rollback and migrate again if the migration fails. ``` - ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13 -r by-dev -o rollback -w milvusdb/milvus:v2.1.1 - ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13 -r by-dev -o migrate -w milvusdb/milvus:v2.4.13 + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13-hotfix -r by-dev -o rollback -w milvusdb/milvus:v2.1.1 + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13-hotfix -r by-dev -o migrate -w milvusdb/milvus:v2.4.13-hotfix ``` diff --git a/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-operator.md b/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-operator.md index 01ce33b70..c0c1561aa 100644 --- a/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-operator.md +++ b/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-operator.md @@ -26,9 +26,9 @@ helm -n milvus-operator upgrade milvus-operator zilliztech-milvus-operator/milvu Once you have upgraded your Milvus operator to the latest version, you have the following choices: -- To upgrade Milvus from v2.2.3 or later releases to 2.4.13, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade). -- To upgrade Milvus from a minor release before v2.2.3 to 2.4.13, you are advised to [upgrade Milvus by changing its image version](#Upgrade-Milvus-by-changing-its-image). -- To upgrade Milvus from v2.1.x to 2.4.13, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade. +- To upgrade Milvus from v2.2.3 or later releases to 2.4.13-hotfix, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade). +- To upgrade Milvus from a minor release before v2.2.3 to 2.4.13-hotfix, you are advised to [upgrade Milvus by changing its image version](#Upgrade-Milvus-by-changing-its-image). +- To upgrade Milvus from v2.1.x to 2.4.13-hotfix, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade. ## Conduct a rolling upgrade @@ -47,7 +47,7 @@ spec: components: enableRollingUpdate: true imageUpdateMode: rollingUpgrade # Default value, can be omitted - image: milvusdb/milvus:v2.4.13 + image: milvusdb/milvus:v2.4.13-hotfix ``` In this above configuration file, set `spec.components.enableRollingUpdate` to `true` and set `spec.components.image` to the desired Milvus version. @@ -63,7 +63,7 @@ spec: components: enableRollingUpdate: true imageUpdateMode: all - image: milvusdb/milvus:v2.4.13 + image: milvusdb/milvus:v2.4.13-hotfix ``` You can set `spec.components.imageUpdateMode` to `rollingDowngrade` to have Milvus replace coordinator pod images with a lower version. @@ -101,7 +101,7 @@ metadata: spec: # Omit other fields ... components: - image: milvusdb/milvus:v2.4.13 + image: milvusdb/milvus:v2.4.13-hotfix ``` Then run the following to perform the upgrade: @@ -112,11 +112,11 @@ kubectl apply -f milvusupgrade.yaml ## Migrate the metadata -Since Milvus 2.2.0, the metadata is incompatible with that in previous releases. The following example snippets assume an upgrade from Milvus 2.1.4 to Milvus 2.4.13. +Since Milvus 2.2.0, the metadata is incompatible with that in previous releases. The following example snippets assume an upgrade from Milvus 2.1.4 to Milvus 2.4.13-hotfix. ### 1. Create a `.yaml` file for metadata migration -Create a metadata migration file. The following is an example. You need to specify the `name`, `sourceVersion`, and `targetVersion` in the configuration file. The following example sets the `name` to `my-release-upgrade`, `sourceVersion` to `v2.1.4`, and `targetVersion` to `v2.4.13`. This means that your Milvus cluster will be upgraded from v2.1.4 to v2.4.13. +Create a metadata migration file. The following is an example. You need to specify the `name`, `sourceVersion`, and `targetVersion` in the configuration file. The following example sets the `name` to `my-release-upgrade`, `sourceVersion` to `v2.1.4`, and `targetVersion` to `v2.4.13-hotfix`. This means that your Milvus cluster will be upgraded from v2.1.4 to v2.4.13-hotfix. ``` apiVersion: milvus.io/v1beta1 @@ -128,9 +128,9 @@ spec: namespace: default name: my-release sourceVersion: "v2.1.4" - targetVersion: "v2.4.13" + targetVersion: "v2.4.13-hotfix" # below are some omit default values: - # targetImage: "milvusdb/milvus:v2.4.13" + # targetImage: "milvusdb/milvus:v2.4.13-hotfix" # toolImage: "milvusdb/meta-migration:v2.2.0" # operation: upgrade # rollbackIfFailed: true diff --git a/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-docker.md b/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-docker.md index 3a8b59629..a2811b81d 100644 --- a/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-docker.md +++ b/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-docker.md @@ -14,7 +14,7 @@ title: Upgrade Milvus Standalone with Docker Compose This topic describes how to upgrade your Milvus using Docker Compose. -In normal cases, you can [upgrade Milvus by changing its image](#Upgrade-Milvus-by-changing-its-image). However, you need to [migrate the metadata](#Migrate-the-metadata) before any upgrade from v2.1.x to v2.4.13. +In normal cases, you can [upgrade Milvus by changing its image](#Upgrade-Milvus-by-changing-its-image). However, you need to [migrate the metadata](#Migrate-the-metadata) before any upgrade from v2.1.x to v2.4.13-hotfix.
@@ -32,7 +32,7 @@ In normal cases, you can upgrade Milvus as follows: ... standalone: container_name: milvus-standalone - image: milvusdb/milvus:v2.4.13 + image: milvusdb/milvus:v2.4.13-hotfix ``` 2. Run the following commands to perform the upgrade. @@ -60,7 +60,7 @@ In normal cases, you can upgrade Milvus as follows: runWithBackup: true config: sourceVersion: 2.1.4 # Specify your milvus version - targetVersion: 2.4.13 + targetVersion: 2.4.13-hotfix backupFilePath: /tmp/migration.bak metastore: type: etcd diff --git a/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md b/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md index 25e100e93..171af4dc5 100644 --- a/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md +++ b/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md @@ -76,11 +76,11 @@ zilliztech/milvus 4.1.0 2.3.0 Milvus is an ope You can choose the upgrade path for your Milvus as follows: -
- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.4.13.
+
- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.4.13-hotfix.
-- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.4.13. +- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.4.13-hotfix. -- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.4.13. +- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.4.13-hotfix.
@@ -102,10 +102,10 @@ The script applies only to the upgrade of Milvus installed with Helm. The follow | `w` | New Milvus image tag | `milvusdb/milvus:v2.2.3` | True | | `o` | Operation | `update` | False | -Once you have ensured that all deployments in your Milvus instance are in their normal status. You can run the following command to upgrade the Milvus instance to 2.4.13. +Once you have ensured that all deployments in your Milvus instance are in their normal status. You can run the following command to upgrade the Milvus instance to 2.4.13-hotfix. ```shell -sh rollingUpdate.sh -n default -i my-release -o update -t 2.4.13 -w 'milvusdb/milvus:v2.4.13' +sh rollingUpdate.sh -n default -i my-release -o update -t 2.4.13-hotfix -w 'milvusdb/milvus:v2.4.13-hotfix' ```
@@ -193,42 +193,42 @@ The following table lists the operations you can do for meta migration. 4. Migrate the Milvus metadata. 5. Start Milvus components with a new image. -#### 2. Upgrade Milvus from v2.1.x to 2.4.13 +#### 2. Upgrade Milvus from v2.1.x to 2.4.13-hotfix -The following commands assume that you upgrade Milvus from v2.1.4 to 2.4.13. Change them to the versions that fit your needs. +The following commands assume that you upgrade Milvus from v2.1.4 to 2.4.13-hotfix. Change them to the versions that fit your needs. 1. Specify Milvus instance name, source Milvus version, and target Milvus version. ``` - ./migrate.sh -i my-release -s 2.1.4 -t 2.4.13 + ./migrate.sh -i my-release -s 2.1.4 -t 2.4.13-hotfix ``` 2. Specify the namespace with `-n` if your Milvus is not installed in the default K8s namespace. ``` - ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13 + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13-hotfix ``` 3. Specify the root path with `-r` if your Milvus is installed with the custom `rootpath`. ``` - ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13 -r by-dev + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13-hotfix -r by-dev ``` 4. Specify the image tag with `-w` if your Milvus is installed with a custom `image`. ``` - ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13 -r by-dev -w milvusdb/milvus:v2.4.13 + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13-hotfix -r by-dev -w milvusdb/milvus:v2.4.13-hotfix ``` 5. Set `-d true` if you want to automatically remove the migration pod after the migration is completed. ``` - ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13 -w milvusdb/milvus:v2.4.13 -d true + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13-hotfix -w milvusdb/milvus:v2.4.13-hotfix -d true ``` 6. Rollback and migrate again if the migration fails. ``` - ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13 -r by-dev -o rollback -w milvusdb/milvus:v2.1.1 - ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13 -r by-dev -o migrate -w milvusdb/milvus:v2.4.13 + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13-hotfix -r by-dev -o rollback -w milvusdb/milvus:v2.1.1 + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.13-hotfix -r by-dev -o migrate -w milvusdb/milvus:v2.4.13-hotfix diff --git a/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-operator.md b/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-operator.md index b9cf65123..8edfe184d 100644 --- a/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-operator.md +++ b/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-operator.md @@ -26,9 +26,9 @@ helm -n milvus-operator upgrade milvus-operator zilliztech-milvus-operator/milvu Once you have upgraded your Milvus operator to the latest version, you have the following choices: -- To upgrade Milvus from v2.2.3 or later releases to 2.4.13, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade). -- To upgrade Milvus from a minor release before v2.2.3 to 2.4.13, you are advised to [upgrade Milvus by changing its image version](#Upgrade-Milvus-by-changing-its-image). -- To upgrade Milvus from v2.1.x to 2.4.13, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade. +- To upgrade Milvus from v2.2.3 or later releases to 2.4.13-hotfix, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade). +- To upgrade Milvus from a minor release before v2.2.3 to 2.4.13-hotfix, you are advised to [upgrade Milvus by changing its image version](#Upgrade-Milvus-by-changing-its-image). +- To upgrade Milvus from v2.1.x to 2.4.13-hotfix, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade. ## Conduct a rolling upgrade @@ -47,7 +47,7 @@ spec: components: enableRollingUpdate: true imageUpdateMode: rollingUpgrade # Default value, can be omitted - image: milvusdb/milvus:v2.4.13 + image: milvusdb/milvus:v2.4.13-hotfix ``` In this above configuration file, set `spec.components.enableRollingUpdate` to `true` and set `spec.components.image` to the desired Milvus version. @@ -63,7 +63,7 @@ spec: components: enableRollingUpdate: true imageUpdateMode: all - image: milvusdb/milvus:v2.4.13 + image: milvusdb/milvus:v2.4.13-hotfix ``` You can set `spec.components.imageUpdateMode` to `rollingDowngrade` to have Milvus replace coordinator pod images with a lower version. @@ -102,7 +102,7 @@ labels: spec: # Omit other fields ... components: - image: milvusdb/milvus:v2.4.13 + image: milvusdb/milvus:v2.4.13-hotfix ``` Then run the following to perform the upgrade: @@ -113,11 +113,11 @@ kubectl apply -f milvusupgrade.yaml ## Migrate the metadata -Since Milvus 2.2.0, the metadata is incompatible with that in previous releases. The following example snippets assume an upgrade from Milvus 2.1.4 to Milvus v2.4.13. +Since Milvus 2.2.0, the metadata is incompatible with that in previous releases. The following example snippets assume an upgrade from Milvus 2.1.4 to Milvus v2.4.13-hotfix. ### 1. Create a `.yaml` file for metadata migration -Create a metadata migration file. The following is an example. You need to specify the `name`, `sourceVersion`, and `targetVersion` in the configuration file. The following example sets the `name` to `my-release-upgrade`, `sourceVersion` to `v2.1.4`, and `targetVersion` to `v2.4.13`. This means that your Milvus instance will be upgraded from v2.1.4 to v2.4.13. +Create a metadata migration file. The following is an example. You need to specify the `name`, `sourceVersion`, and `targetVersion` in the configuration file. The following example sets the `name` to `my-release-upgrade`, `sourceVersion` to `v2.1.4`, and `targetVersion` to `v2.4.13-hotfix`. This means that your Milvus instance will be upgraded from v2.1.4 to v2.4.13-hotfix. ``` apiVersion: milvus.io/v1beta1 @@ -129,9 +129,9 @@ spec: namespace: default name: my-release sourceVersion: "v2.1.4" - targetVersion: "v2.4.13" + targetVersion: "v2.4.13-hotfix" # below are some omit default values: - # targetImage: "milvusdb/milvus:v2.4.13" + # targetImage: "milvusdb/milvus:v2.4.13-hotfix" # toolImage: "milvusdb/meta-migration:v2.2.0" # operation: upgrade # rollbackIfFailed: true diff --git a/v2.4.x/site/en/getstarted/run-milvus-docker/install_standalone-docker-compose.md b/v2.4.x/site/en/getstarted/run-milvus-docker/install_standalone-docker-compose.md index 6de8da591..66b22e604 100644 --- a/v2.4.x/site/en/getstarted/run-milvus-docker/install_standalone-docker-compose.md +++ b/v2.4.x/site/en/getstarted/run-milvus-docker/install_standalone-docker-compose.md @@ -21,7 +21,7 @@ Milvus provides a Docker Compose configuration file in the Milvus repository. To ```shell # Download the configuration file -$ wget https://github.com/milvus-io/milvus/releases/download/v2.4.13/milvus-standalone-docker-compose.yml -O docker-compose.yml +$ wget https://github.com/milvus-io/milvus/releases/download/v2.4.13-hotfix/milvus-standalone-docker-compose.yml -O docker-compose.yml # Start Milvus $ sudo docker-compose up -d diff --git a/v2.4.x/site/en/getstarted/run-milvus-gpu/install_standalone-docker-compose-gpu.md b/v2.4.x/site/en/getstarted/run-milvus-gpu/install_standalone-docker-compose-gpu.md index 79243c242..e60e58061 100644 --- a/v2.4.x/site/en/getstarted/run-milvus-gpu/install_standalone-docker-compose-gpu.md +++ b/v2.4.x/site/en/getstarted/run-milvus-gpu/install_standalone-docker-compose-gpu.md @@ -27,10 +27,10 @@ To install Milvus with GPU support using Docker Compose, follow these steps. ### 1. Download and configure the YAML file -Download [`milvus-standalone-docker-compose-gpu.yml`](https://github.com/milvus-io/milvus/releases/download/v2.4.13/milvus-standalone-docker-compose-gpu.yml) and save it as docker-compose.yml manually, or with the following command. +Download [`milvus-standalone-docker-compose-gpu.yml`](https://github.com/milvus-io/milvus/releases/download/v2.4.13-hotfix/milvus-standalone-docker-compose-gpu.yml) and save it as docker-compose.yml manually, or with the following command. ```shell -$ wget https://github.com/milvus-io/milvus/releases/download/v2.4.13/milvus-standalone-docker-compose-gpu.yml -O docker-compose.yml +$ wget https://github.com/milvus-io/milvus/releases/download/v2.4.13-hotfix/milvus-standalone-docker-compose-gpu.yml -O docker-compose.yml ``` You need to make some changes to the environment variables of the standalone service in the YAML file as follows: diff --git a/v2.4.x/site/en/release_notes.md b/v2.4.x/site/en/release_notes.md index ee798d132..15a8a86dc 100644 --- a/v2.4.x/site/en/release_notes.md +++ b/v2.4.x/site/en/release_notes.md @@ -7,7 +7,21 @@ title: Release Notes Find out what’s new in Milvus! This page summarizes new features, improvements, known issues, and bug fixes in each release. You can find the release notes for each released version after v2.4.0 in this section. We suggest that you regularly visit this page to learn about updates. -## v2.4.13 +## v2.4.13-hotfix + +Release Date: October 17, 2024 + +| Milvus version | Python SDK version | Java SDK version | Node.js SDK version | +|----------------|--------------------|------------------|---------------------| +| 2.4.13-hotfix | 2.4.8 | 2.4.5 | 2.4.9 | + +Milvus v2.4.13-hotfix addresses a critical issue specific to v2.4.13, where Milvus may fail to retrieve collection information after a restart if all MetaKV snapshots were garbage-collected ([#36933](https://github.com/milvus-io/milvus/pull/36933)). Users currently running v2.4.13 are advised to upgrade to v2.4.13-hotfix at the earliest opportunity to avoid potential disruptions. + +### Critical fixes + +- Load original key if timestamp is MaxTimestamp ([#36935](https://github.com/milvus-io/milvus/pull/36935)) + +## [Deprecated] v2.4.13 Release Date: October 12, 2024