From 872990da408af797ec3045a25e615cc18c92d045 Mon Sep 17 00:00:00 2001 From: Milvus-doc-bot Date: Wed, 23 Aug 2023 14:36:56 +0000 Subject: [PATCH] Release new docs --- v2.2.x/Variables.json | 10 ++--- v2.2.x/site/en/adminGuide/configure-docker.md | 10 ++--- v2.2.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 +++++----- v2.2.x/site/en/getstarted/example_code.md | 2 +- .../standalone/install_standalone-docker.md | 4 +- v2.2.x/site/en/reference/disk_index.md | 9 +++++ v2.2.x/site/en/release_notes.md | 40 +++++++++++++++++++ .../en/userGuide/tools/attu_install-docker.md | 10 ++--- .../userGuide/tools/milvus_backup_overview.md | 2 +- 15 files changed, 130 insertions(+), 81 deletions(-) diff --git a/v2.2.x/Variables.json b/v2.2.x/Variables.json index 88856a840..3f9ab32f7 100644 --- a/v2.2.x/Variables.json +++ b/v2.2.x/Variables.json @@ -1,6 +1,6 @@ { - "milvus_release_version": "2.2.13", - "milvus_release_tag": "2.2.13", + "milvus_release_version": "2.2.14", + "milvus_release_tag": "2.2.14", "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.2.x", @@ -10,7 +10,7 @@ "milvus_restful_sdk_version": "2.2.x", "milvus_operator_version": "0.7.17", "milvus_helm_chart_version": "4.0.32", - "milvus_image": "2.2.13", - "attu_release": "2.2.7", - "milvus_backup_release": "0.3.0" + "milvus_image": "2.2.14", + "attu_release": "2.2.8", + "milvus_backup_release": "0.3.2" } diff --git a/v2.2.x/site/en/adminGuide/configure-docker.md b/v2.2.x/site/en/adminGuide/configure-docker.md index 8d9bdeccf..61bc34820 100644 --- a/v2.2.x/site/en/adminGuide/configure-docker.md +++ b/v2.2.x/site/en/adminGuide/configure-docker.md @@ -15,10 +15,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.2.13/configs/milvus.yaml) `milvus.yaml` directly or with the following command. +[Download](https://raw.githubusercontent.com/milvus-io/milvus/v2.2.14/configs/milvus.yaml) `milvus.yaml` directly or with the following command. ``` -$ wget https://raw.githubusercontent.com/milvus-io/milvus/v2.2.13/configs/milvus.yaml +$ wget https://raw.githubusercontent.com/milvus-io/milvus/v2.2.14/configs/milvus.yaml ``` ## Modify the configuration file @@ -171,13 +171,13 @@ Sorted by: ## Download an installation file -Download the installation file for Milvus [standalone](https://github.com/milvus-io/milvus/releases/download/v2.2.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.2.14/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.2.13/milvus-standalone-docker-compose.yml -O docker-compose.yml +$ wget https://github.com/milvus-io/milvus/releases/download/v2.2.14/milvus-standalone-docker-compose.yml -O docker-compose.yml ``` ## Modify the installation file @@ -190,7 +190,7 @@ Map the local path to your `milvus.yaml` file onto the corresponding docker cont ... proxy: container_name: milvus-proxy - image: milvusdb/milvus:v2.2.13 + image: milvusdb/milvus:v2.2.14 command: ["milvus", "run", "proxy"] volumes: # Add a volumes section. - /local/path/to/your/milvus.yaml:/milvus/configs/milvus.yaml # Map the local path to the container path diff --git a/v2.2.x/site/en/adminGuide/operator.md b/v2.2.x/site/en/adminGuide/operator.md index 0a3e50340..cd108e422 100644 --- a/v2.2.x/site/en/adminGuide/operator.md +++ b/v2.2.x/site/en/adminGuide/operator.md @@ -11,7 +11,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.2.x/site/en/adminGuide/upgrade_milvus_cluster-docker.md b/v2.2.x/site/en/adminGuide/upgrade_milvus_cluster-docker.md index bc3640034..3b3e64bdb 100644 --- a/v2.2.x/site/en/adminGuide/upgrade_milvus_cluster-docker.md +++ b/v2.2.x/site/en/adminGuide/upgrade_milvus_cluster-docker.md @@ -9,7 +9,7 @@ summary: Learn how to 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.2.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.2.14. ## Upgrade Milvus by changing its image @@ -23,35 +23,35 @@ In normal cases, you can upgrade Milvus as follows: ... rootcoord: container_name: milvus-rootcoord - image: milvusdb/milvus:v2.2.13 + image: milvusdb/milvus:v2.2.14 ... proxy: container_name: milvus-proxy - image: milvusdb/milvus:v2.2.13 + image: milvusdb/milvus:v2.2.14 ... querycoord: container_name: milvus-querycoord - image: milvusdb/milvus:v2.2.13 + image: milvusdb/milvus:v2.2.14 ... querynode: container_name: milvus-querynode - image: milvusdb/milvus:v2.2.13 + image: milvusdb/milvus:v2.2.14 ... indexcoord: container_name: milvus-indexcoord - image: milvusdb/milvus:v2.2.13 + image: milvusdb/milvus:v2.2.14 ... indexnode: container_name: milvus-indexnode - image: milvusdb/milvus:v2.2.13 + image: milvusdb/milvus:v2.2.14 ... datacoord: container_name: milvus-datacoord - image: milvusdb/milvus:v2.2.13 + image: milvusdb/milvus:v2.2.14 ... datanode: container_name: milvus-datanode - image: milvusdb/milvus:v2.2.13 + image: milvusdb/milvus:v2.2.14 ``` 2. Run the following commands to perform the upgrade. @@ -79,7 +79,7 @@ In normal cases, you can upgrade Milvus as follows: runWithBackup: true config: sourceVersion: 2.1.4 # Specify your milvus version - targetVersion: 2.2.13 + targetVersion: 2.2.14 backupFilePath: /tmp/migration.bak metastore: type: etcd diff --git a/v2.2.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md b/v2.2.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md index cf6f0f126..501356c5a 100644 --- a/v2.2.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md +++ b/v2.2.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md @@ -53,9 +53,9 @@ zilliztech/milvus 4.0.23 2.2.9 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.2.13. -- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.2.13. -- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.2.13. +- [Conduct a rolling upgrade](#Conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.2.14. +- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.2.14. +- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.2.14.
@@ -77,10 +77,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.2.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.2.14. ```shell -sh rollingUpdate.sh -n default -i my-release -o update -t 2.2.13 -w 'milvusdb/milvus:v2.2.13' +sh rollingUpdate.sh -n default -i my-release -o update -t 2.2.14 -w 'milvusdb/milvus:v2.2.14' ```
@@ -190,43 +190,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.2.13 +#### 2. Upgrade Milvus from v2.1.x to 2.2.14 -The following commands assume that you upgrade Milvus from v2.1.4 to 2.2.13. Change them to the versions that fit your needs. +The following commands assume that you upgrade Milvus from v2.1.4 to 2.2.14. 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.2.13 + ./migrate.sh -i my-release -s 2.1.4 -t 2.2.14 ``` 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.2.13 + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.14 ``` 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.2.13 -r by-dev + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.14 -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.2.13 -r by-dev -w milvusdb/milvus:v2.2.13 + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.14 -r by-dev -w milvusdb/milvus:v2.2.14 ``` 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.2.13 -w milvusdb/milvus:v2.2.13 -d true + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.14 -w milvusdb/milvus:v2.2.14 -d true ``` 6. Rollback and migrate again if the migration fails. ``` - ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.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.2.13 -r by-dev -o migrate -w milvusdb/milvus:v2.2.13 + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.14 -r by-dev -o rollback -w milvusdb/milvus:v2.1.1 + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.14 -r by-dev -o migrate -w milvusdb/milvus:v2.2.14 ``` diff --git a/v2.2.x/site/en/adminGuide/upgrade_milvus_cluster-operator.md b/v2.2.x/site/en/adminGuide/upgrade_milvus_cluster-operator.md index a61579f34..609bf69e7 100644 --- a/v2.2.x/site/en/adminGuide/upgrade_milvus_cluster-operator.md +++ b/v2.2.x/site/en/adminGuide/upgrade_milvus_cluster-operator.md @@ -25,9 +25,9 @@ helm -n milvus-operator upgrade milvus-operator milvus-operator/milvus-operator 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.2.13, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade). -- To upgrade Milvus from a minor release before v2.2.3 to 2.2.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.2.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.2.14, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade). +- To upgrade Milvus from a minor release before v2.2.3 to 2.2.14, 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.2.14, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade. ## Conduct a rolling upgrade @@ -46,7 +46,7 @@ spec: components: enableRollingUpdate: true imageUpdateMode: rollingUpgrade # Default value, can be omitted - image: milvusdb/milvus:v2.2.13 + image: milvusdb/milvus:v2.2.14 ``` In this above configuration file, set `spec.components.enableRollingUpdate` to `true` and set `spec.components.image` to the desired Milvus version. @@ -62,7 +62,7 @@ spec: components: enableRollingUpdate: true imageUpdateMode: all - image: milvusdb/milvus:v2.2.13 + image: milvusdb/milvus:v2.2.14 ``` You can set `spec.components.imageUpdateMode` to `rollingDowngrade` to have Milvus replace coordinator pod images with a lower version. @@ -100,7 +100,7 @@ metadata: spec: # Omit other fields ... components: - image: milvusdb/milvus:v2.2.13 + image: milvusdb/milvus:v2.2.14 ``` Then run the following to perform the upgrade: @@ -111,11 +111,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.2.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.2.14. ### 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.2.13`. This means that your Milvus cluster will be upgraded from v2.1.4 to v2.2.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.2.14`. This means that your Milvus cluster will be upgraded from v2.1.4 to v2.2.14. ``` apiVersion: milvus.io/v1beta1 @@ -127,9 +127,9 @@ spec: namespace: default name: my-release sourceVersion: "v2.1.4" - targetVersion: "v2.2.13" + targetVersion: "v2.2.14" # below are some omit default values: - # targetImage: "milvusdb/milvus:v2.2.13" + # targetImage: "milvusdb/milvus:v2.2.14" # toolImage: "milvusdb/meta-migration:v2.2.0" # operation: upgrade # rollbackIfFailed: true diff --git a/v2.2.x/site/en/adminGuide/upgrade_milvus_standalone-docker.md b/v2.2.x/site/en/adminGuide/upgrade_milvus_standalone-docker.md index 66aaf1e2a..7f838f9a9 100644 --- a/v2.2.x/site/en/adminGuide/upgrade_milvus_standalone-docker.md +++ b/v2.2.x/site/en/adminGuide/upgrade_milvus_standalone-docker.md @@ -13,7 +13,7 @@ summary: Learn how to 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.2.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.2.14.
@@ -31,7 +31,7 @@ In normal cases, you can upgrade Milvus as follows: ... standalone: container_name: milvus-standalone - image: milvusdb/milvus:v2.2.13 + image: milvusdb/milvus:v2.2.14 ``` 2. Run the following commands to perform the upgrade. @@ -59,7 +59,7 @@ In normal cases, you can upgrade Milvus as follows: runWithBackup: true config: sourceVersion: 2.1.4 # Specify your milvus version - targetVersion: 2.2.13 + targetVersion: 2.2.14 backupFilePath: /tmp/migration.bak metastore: type: etcd diff --git a/v2.2.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md b/v2.2.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md index 119cfe4d2..1aface86c 100644 --- a/v2.2.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md +++ b/v2.2.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md @@ -54,9 +54,9 @@ zilliztech/milvus 4.0.23 2.2.9 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.2.13. -- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.2.13. -- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.2.13. +- [Conduct a rolling upgrade](#Conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.2.14. +- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.2.14. +- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.2.14.
@@ -78,10 +78,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.2.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.2.14. ```shell -sh rollingUpdate.sh -n default -i my-release -o update -t 2.2.13 -w 'milvusdb/milvus:v2.2.13' +sh rollingUpdate.sh -n default -i my-release -o update -t 2.2.14 -w 'milvusdb/milvus:v2.2.14' ```
@@ -169,42 +169,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.2.13 +#### 2. Upgrade Milvus from v2.1.x to 2.2.14 -The following commands assume that you upgrade Milvus from v2.1.4 to 2.2.13. Change them to the versions that fit your needs. +The following commands assume that you upgrade Milvus from v2.1.4 to 2.2.14. 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.2.13 + ./migrate.sh -i my-release -s 2.1.4 -t 2.2.14 ``` 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.2.13 + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.14 ``` 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.2.13 -r by-dev + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.14 -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.2.13 -r by-dev -w milvusdb/milvus:v2.2.13 + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.14 -r by-dev -w milvusdb/milvus:v2.2.14 ``` 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.2.13 -w milvusdb/milvus:v2.2.13 -d true + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.14 -w milvusdb/milvus:v2.2.14 -d true ``` 6. Rollback and migrate again if the migration fails. ``` - ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.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.2.13 -r by-dev -o migrate -w milvusdb/milvus:v2.2.13 + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.14 -r by-dev -o rollback -w milvusdb/milvus:v2.1.1 + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.14 -r by-dev -o migrate -w milvusdb/milvus:v2.2.14 diff --git a/v2.2.x/site/en/adminGuide/upgrade_milvus_standalone-operator.md b/v2.2.x/site/en/adminGuide/upgrade_milvus_standalone-operator.md index 070c39c17..196e79f3f 100644 --- a/v2.2.x/site/en/adminGuide/upgrade_milvus_standalone-operator.md +++ b/v2.2.x/site/en/adminGuide/upgrade_milvus_standalone-operator.md @@ -25,9 +25,9 @@ helm -n milvus-operator upgrade milvus-operator milvus-operator/milvus-operator 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.2.13, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade). -- To upgrade Milvus from a minor release before v2.2.3 to 2.2.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.2.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.2.14, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade). +- To upgrade Milvus from a minor release before v2.2.3 to 2.2.14, 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.2.14, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade. ## Conduct a rolling upgrade @@ -46,7 +46,7 @@ spec: components: enableRollingUpdate: true imageUpdateMode: rollingUpgrade # Default value, can be omitted - image: milvusdb/milvus:v2.2.13 + image: milvusdb/milvus:v2.2.14 ``` In this above configuration file, set `spec.components.enableRollingUpdate` to `true` and set `spec.components.image` to the desired Milvus version. @@ -62,7 +62,7 @@ spec: components: enableRollingUpdate: true imageUpdateMode: all - image: milvusdb/milvus:v2.2.13 + image: milvusdb/milvus:v2.2.14 ``` You can set `spec.components.imageUpdateMode` to `rollingDowngrade` to have Milvus replace coordinator pod images with a lower version. @@ -101,7 +101,7 @@ app: milvus spec: # Omit other fields ... components: - image: milvusdb/milvus:v2.2.13 + image: milvusdb/milvus:v2.2.14 ``` 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 v2.2.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.2.14. ### 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.2.13`. This means that your Milvus instance will be upgraded from v2.1.4 to v2.2.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.2.14`. This means that your Milvus instance will be upgraded from v2.1.4 to v2.2.14. ``` apiVersion: milvus.io/v1beta1 @@ -128,9 +128,9 @@ spec: namespace: default name: my-release sourceVersion: "v2.1.4" - targetVersion: "v2.2.13" + targetVersion: "v2.2.14" # below are some omit default values: - # targetImage: "milvusdb/milvus:v2.2.13" + # targetImage: "milvusdb/milvus:v2.2.14" # toolImage: "milvusdb/meta-migration:v2.2.0" # operation: upgrade # rollbackIfFailed: true diff --git a/v2.2.x/site/en/getstarted/example_code.md b/v2.2.x/site/en/getstarted/example_code.md index e793f60d9..679e08c8c 100644 --- a/v2.2.x/site/en/getstarted/example_code.md +++ b/v2.2.x/site/en/getstarted/example_code.md @@ -17,7 +17,7 @@ Through running the example code we provided, you will have a primary understand ## Preparations -- [Milvus 2.2.13](install_standalone-docker.md) +- [Milvus 2.2.14](install_standalone-docker.md) - Python 3 (3.7.1 or later) - [PyMilvus 2.2.x](install-pymilvus.md) diff --git a/v2.2.x/site/en/getstarted/standalone/install_standalone-docker.md b/v2.2.x/site/en/getstarted/standalone/install_standalone-docker.md index fb2d31d80..55cbf4091 100644 --- a/v2.2.x/site/en/getstarted/standalone/install_standalone-docker.md +++ b/v2.2.x/site/en/getstarted/standalone/install_standalone-docker.md @@ -21,10 +21,10 @@ For the users using MacOS 10.14 or later, set the Docker virtual machine (VM) to ## Download the `YAML` file -[Download](https://github.com/milvus-io/milvus/releases/download/v2.2.13/milvus-standalone-docker-compose.yml) `milvus-standalone-docker-compose.yml` and save it as `docker-compose.yml` manually, or with the following command. +[Download](https://github.com/milvus-io/milvus/releases/download/v2.2.14/milvus-standalone-docker-compose.yml) `milvus-standalone-docker-compose.yml` and save it as `docker-compose.yml` manually, or with the following command. ``` -$ wget https://github.com/milvus-io/milvus/releases/download/v2.2.13/milvus-standalone-docker-compose.yml -O docker-compose.yml +$ wget https://github.com/milvus-io/milvus/releases/download/v2.2.14/milvus-standalone-docker-compose.yml -O docker-compose.yml ``` ## Start Milvus diff --git a/v2.2.x/site/en/reference/disk_index.md b/v2.2.x/site/en/reference/disk_index.md index f4b5ad339..4b56783c6 100644 --- a/v2.2.x/site/en/reference/disk_index.md +++ b/v2.2.x/site/en/reference/disk_index.md @@ -70,3 +70,12 @@ DiskIndex: | `LoadNumThreadRatio` | Ratio between the number of threads used to load index/search and the number of CPUs. For details, refer to the first item in [References and Facts](disk_index.md#references-and-facts). | [1, 65536 / 32 / CPU number] | 8.0 | | `BeamWidthRatio` | Ratio between the maximum number of IO requests per search iteration and CPU number. | [1, max(128 / CPU number, 16)] | 4.0 | +## Troubleshooting + +- How to deal with the `io_setup() failed; returned -11, errno=11:Resource temporarily unavailable` error? + + The Linux kernel provides the Asynchronous non-blocking I/O (AIO) feature that allows a process to initiate multiple I/O operations simultaneously without having to wait for any of them to complete. This helps boost performance for applications that can overlap processing and I/O. + + The performance can be tuned using the `/proc/sys/fs/aio-max-nr` virtual file in the proc file system. The `aio-max-nr` parameter determines the maximum number of allowable concurrent requests. + + The `aio-max-nr` defaults to `65535`, you can set it up to `10485760`. \ No newline at end of file diff --git a/v2.2.x/site/en/release_notes.md b/v2.2.x/site/en/release_notes.md index 4a4126e1a..bd9228203 100644 --- a/v2.2.x/site/en/release_notes.md +++ b/v2.2.x/site/en/release_notes.md @@ -6,6 +6,46 @@ summary: Milvus 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.2.0 in this section. We suggest that you regularly visit this page to learn about updates. +## 2.2.14 + +Release date: Aug 23, 2023 + +| Milvus version | Python SDK version | Java SDK version | Go SDK version | Node.js SDK version | +| -------------- | ------------------ | ---------------- | -------------- | ------------------- | +| 2.2.14 | 2.2.15 | 2.2.11 | 2.2.7 | 2.2.24 | + +Milvus 2.2.14 is a minor bug-fix release that mainly addresses cluster unavailability issues during rolling upgrades. With this new release, Milvus deployed with Kubernetes operator can be upgraded with almost zero downtime. + +### Bug Fixes + +This update addresses the following issues: + +- Fixed the issues that caused rolling upgrades to take longer than expected: + - Changed the default `gracefulStopTimeout` and now only displays a warning when there is a failure to refresh the policy cache. ([#26443](https://github.com/milvus-io/milvus/pull/26443)) + - Refined gRPC retries. ([#26464](https://github.com/milvus-io/milvus/pull/26464)) + - Checked and reset the gRPC client server ID if it mismatches with the session. ([#26473](https://github.com/milvus-io/milvus/pull/26473)) + - Added a server ID validation interceptor. ([#26395](https://github.com/milvus-io/milvus/pull/26395)) ([#26424](https://github.com/milvus-io/milvus/pull/26424)) + - Improved the performance of the server ID interceptor validation. ([#26468](https://github.com/milvus-io/milvus/pull/26468)) ([#26496](https://github.com/milvus-io/milvus/pull/26496)) +- Fixed the expression incompatibility issue between the parser and the executor. ([#26493](https://github.com/milvus-io/milvus/pull/26493)) ([#26495](https://github.com/milvus-io/milvus/pull/26495)) +- Fixed failures in serializing string index when its size exceeds 2 GB. ([#26393](https://github.com/milvus-io/milvus/pull/26393)) +- Fixed issues where enormous duplicate collections were being re-dropped during restore. ([#26030](https://github.com/milvus-io/milvus/pull/26030)) +- Fixed the issue where the leader view returns a loading shard cluster. ([#26263](https://github.com/milvus-io/milvus/pull/26263)) +- Fixed the Liveness check block in SessionUtil to watch forever. ([#26250](https://github.com/milvus-io/milvus/pull/26250)) +- Fixed issues related to logical expressions. ([#26513](https://github.com/milvus-io/milvus/pull/26513)) ([#26515](https://github.com/milvus-io/milvus/pull/26515)) +- Fixed issues related to continuous restart of DataNode/DataCoord. [#26470](https://github.com/milvus-io/milvus/pull/26470) ([#26506](https://github.com/milvus-io/milvus/pull/26506)) +- Fixed issues related to being stuck in channel checkpoint. ([#26544](https://github.com/milvus-io/milvus/pull/26544)) +- Fixed an issue so that Milvus considers the balance task with a released source segment as stale. ([#26498](https://github.com/milvus-io/milvus/pull/26498)) + +### Enhancement + +- Refined error messages for fields that do not exist ([#26331](https://github.com/milvus-io/milvus/pull/26331)). +- Fixed unclear error messages of the proto parser ([#26365](https://github.com/milvus-io/milvus/pull/26365)) ([#26366](https://github.com/milvus-io/milvus/pull/26366)). +- Prohibited setting a partition name for a collection that already has a partition key ([#26128](https://github.com/milvus-io/milvus/pull/26128)). +- Added disk metric information ([#25678](https://github.com/milvus-io/milvus/pull/25678)). +- Fixed the CollectionNotExists error during vector search and retrieval ([#26532](https://github.com/milvus-io/milvus/pull/26532)). +- Added a default `MALLOC_CONF` environment variable to release memory after dropping a collection ([#26353](https://github.com/milvus-io/milvus/pull/26353)). +- Made pulsar request timeout configurable ([#26526](https://github.com/milvus-io/milvus/pull/26526)). + ## 2.2.13 Release date: Aug 9, 2023 diff --git a/v2.2.x/site/en/userGuide/tools/attu_install-docker.md b/v2.2.x/site/en/userGuide/tools/attu_install-docker.md index 8f2d7b230..f2df06e14 100644 --- a/v2.2.x/site/en/userGuide/tools/attu_install-docker.md +++ b/v2.2.x/site/en/userGuide/tools/attu_install-docker.md @@ -29,12 +29,12 @@ See v2.0.x Attu d | -------------- | ------------------------------ | | v2.0.x | v2.0.5 | | v2.1.x | v2.1.5 | -| v2.2.x | v2.2.7 | +| v2.2.x | v2.2.8 | ## Start an Attu instance ```Apache -docker run -p 8000:3000 -e MILVUS_URL={your machine IP}:19530 zilliz/attu:v2.2.7 +docker run -p 8000:3000 -e MILVUS_URL={your machine IP}:19530 zilliz/attu:v2.2.8 ``` Once you start the docker, visit `http://{ your machine IP }:8000` in your browser, and click **Connect** to enter the Attu service. @@ -46,17 +46,17 @@ And we alsow support TLS connection, username and password. # Install Milvus Standalone and Attu with Docker Compose -[Download](https://github.com/milvus-io/milvus/releases/download/v2.2.13/milvus-standalone-docker-compose.yml) `milvus-standalone-docker-compose.yml` and save it as `docker-compose.yml` manually, or with the following command. +[Download](https://github.com/milvus-io/milvus/releases/download/v2.2.14/milvus-standalone-docker-compose.yml) `milvus-standalone-docker-compose.yml` and save it as `docker-compose.yml` manually, or with the following command. ``` -$ wget https://github.com/milvus-io/milvus/releases/download/v2.2.13/milvus-standalone-docker-compose.yml -O docker-compose.yml +$ wget https://github.com/milvus-io/milvus/releases/download/v2.2.14/milvus-standalone-docker-compose.yml -O docker-compose.yml ``` Edit the downloaded `docker-compose.yml` file using your favorite text editor and add the following to the services block: ``` attu: container_name: attu - image: zilliz/attu:v2.2.7 + image: zilliz/attu:v2.2.8 environment: MILVUS_URL: milvus-standalone:19530 ports: diff --git a/v2.2.x/site/en/userGuide/tools/milvus_backup_overview.md b/v2.2.x/site/en/userGuide/tools/milvus_backup_overview.md index e33248ff1..5100856ae 100644 --- a/v2.2.x/site/en/userGuide/tools/milvus_backup_overview.md +++ b/v2.2.x/site/en/userGuide/tools/milvus_backup_overview.md @@ -26,4 +26,4 @@ To restore from a backup, Milvus Backup creates a new collection in the target M ## Latest release -- [v0.3.0](https://github.com/zilliztech/milvus-backup/releases/tag/v0.3.0) +- [v0.3.2](https://github.com/zilliztech/milvus-backup/releases/tag/v0.3.2)