diff --git a/localization/v2.4.x/site/en/adminGuide/configure-docker.json b/localization/v2.4.x/site/en/adminGuide/configure-docker.json index 616f4b0e4..4345e9efd 100644 --- a/localization/v2.4.x/site/en/adminGuide/configure-docker.json +++ b/localization/v2.4.x/site/en/adminGuide/configure-docker.json @@ -1 +1 @@ -{"codeList":["$ wget https://raw.githubusercontent.com/milvus-io/milvus/v2.4.18/configs/milvus.yaml\n","# For Milvus standalone\n$ wget https://github.com/milvus-io/milvus/releases/download/v2.4.18/milvus-standalone-docker-compose.yml -O docker-compose.yml\n","...\n standalone:\n container_name: milvus-standalone\n image: milvusdb/milvus:v2.2.13\n command: [\"milvus\", \"run\", \"standalone\"]\n environment:\n ETCD_ENDPOINTS: etcd:2379\n MINIO_ADDRESS: minio:9000\n volumes:\n - /local/path/to/your/milvus.yaml:/milvus/configs/milvus.yaml # Map the local path to the container path\n - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/milvus:/var/lib/milvus\n ports:\n - \"19530:19530\"\n - \"9091:9091\"\n depends_on:\n - \"etcd\"\n - \"minio\"\n...\n","$ sudo docker compose up -d\n"],"headingContent":"Configure Milvus with Docker Compose","anchorList":[{"label":"Configure Milvus with Docker Compose","href":"Configure-Milvus-with-Docker-Compose","type":1,"isActive":false},{"label":"Download a configuration file","href":"Download-a-configuration-file","type":2,"isActive":false},{"label":"Modify the configuration file","href":"Modify-the-configuration-file","type":2,"isActive":false},{"label":"Download an installation file","href":"Download-an-installation-file","type":2,"isActive":false},{"label":"Modify the installation file","href":"Modify-the-installation-file","type":2,"isActive":false},{"label":"Start Milvus","href":"Start-Milvus","type":2,"isActive":false},{"label":"What's next","href":"Whats-next","type":2,"isActive":false}]} \ No newline at end of file +{"codeList":["$ wget https://raw.githubusercontent.com/milvus-io/milvus/v2.4.19/configs/milvus.yaml\n","# For Milvus standalone\n$ wget https://github.com/milvus-io/milvus/releases/download/v2.4.19/milvus-standalone-docker-compose.yml -O docker-compose.yml\n","...\n standalone:\n container_name: milvus-standalone\n image: milvusdb/milvus:v2.2.13\n command: [\"milvus\", \"run\", \"standalone\"]\n environment:\n ETCD_ENDPOINTS: etcd:2379\n MINIO_ADDRESS: minio:9000\n volumes:\n - /local/path/to/your/milvus.yaml:/milvus/configs/milvus.yaml # Map the local path to the container path\n - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/milvus:/var/lib/milvus\n ports:\n - \"19530:19530\"\n - \"9091:9091\"\n depends_on:\n - \"etcd\"\n - \"minio\"\n...\n","$ sudo docker compose up -d\n"],"headingContent":"Configure Milvus with Docker Compose","anchorList":[{"label":"Configure Milvus with Docker Compose","href":"Configure-Milvus-with-Docker-Compose","type":1,"isActive":false},{"label":"Download a configuration file","href":"Download-a-configuration-file","type":2,"isActive":false},{"label":"Modify the configuration file","href":"Modify-the-configuration-file","type":2,"isActive":false},{"label":"Download an installation file","href":"Download-an-installation-file","type":2,"isActive":false},{"label":"Modify the installation file","href":"Modify-the-installation-file","type":2,"isActive":false},{"label":"Start Milvus","href":"Start-Milvus","type":2,"isActive":false},{"label":"What's next","href":"Whats-next","type":2,"isActive":false}]} \ No newline at end of file diff --git a/localization/v2.4.x/site/en/adminGuide/configure-docker.md b/localization/v2.4.x/site/en/adminGuide/configure-docker.md index b035c5f8b..d1bb262ff 100644 --- a/localization/v2.4.x/site/en/adminGuide/configure-docker.md +++ b/localization/v2.4.x/site/en/adminGuide/configure-docker.md @@ -39,8 +39,8 @@ In current release, all parameters take effect only after Milvus restarts. d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z" > -

Download milvus.yaml directly or with the following command.

-
$ wget https://raw.githubusercontent.com/milvus-io/milvus/v2.4.18/configs/milvus.yaml
+    

Download milvus.yaml directly or with the following command.

+
$ wget https://raw.githubusercontent.com/milvus-io/milvus/v2.4.19/configs/milvus.yaml
 

Modify the configuration file

Download the installation file for Milvus standalone, and save it as docker-compose.yml.

+

Download the installation file for Milvus standalone, 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.18/milvus-standalone-docker-compose.yml -O docker-compose.yml
+$ wget https://github.com/milvus-io/milvus/releases/download/v2.4.19/milvus-standalone-docker-compose.yml -O docker-compose.yml
 

Modify the installation file

-

All code samples on this page are in PyMilvus 2.4.9. Upgrade your PyMilvus installation before running them.

+

All code samples on this page are in PyMilvus 2.4.13. Upgrade your PyMilvus installation before running them.

  1. Create a resource group.

    diff --git a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-docker.json b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-docker.json index 80ae87604..a23e49bf3 100644 --- a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-docker.json +++ b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-docker.json @@ -1 +1 @@ -{"codeList":["...\nrootcoord:\n container_name: milvus-rootcoord\n image: milvusdb/milvus:v2.4.18\n...\nproxy:\n container_name: milvus-proxy\n image: milvusdb/milvus:v2.4.18\n...\nquerycoord:\n container_name: milvus-querycoord\n image: milvusdb/milvus:v2.4.18 \n...\nquerynode:\n container_name: milvus-querynode\n image: milvusdb/milvus:v2.4.18\n...\nindexcoord:\n container_name: milvus-indexcoord\n image: milvusdb/milvus:v2.4.18\n...\nindexnode:\n container_name: milvus-indexnode\n image: milvusdb/milvus:v2.4.18 \n...\ndatacoord:\n container_name: milvus-datacoord\n image: milvusdb/milvus:v2.4.18 \n...\ndatanode:\n container_name: milvus-datanode\n image: milvusdb/milvus:v2.4.18\n","docker compose down\ndocker compose up -d\n","docker stop \n","# migration.yaml\ncmd:\n # Option: run/backup/rollback\n type: run\n runWithBackup: true\nconfig:\n sourceVersion: 2.1.4 # Specify your milvus version\n targetVersion: 2.4.18\n backupFilePath: /tmp/migration.bak\nmetastore:\n type: etcd\netcd:\n endpoints:\n - milvus-etcd:2379 # Use the etcd container name\n rootPath: by-dev # The root path where data is stored in etcd\n metaSubPath: meta\n kvSubPath: kv\n","# Suppose your docker-compose run with the default milvus network,\n# and you put migration.yaml in the same directory with docker-compose.yaml.\ndocker run --rm -it --network milvus -v $(pwd)/migration.yaml:/milvus/configs/migration.yaml milvus/meta-migration:v2.2.0 /milvus/bin/meta-migration -config=/milvus/configs/migration.yaml\n","Update the milvus image tag in the docker-compose.yaml\ndocker compose down\ndocker compose up -d\n"],"headingContent":"Upgrade Milvus Cluster with Docker Compose","anchorList":[{"label":"Upgrade Milvus Cluster with Docker Compose","href":"Upgrade-Milvus-Cluster-with-Docker-Compose","type":1,"isActive":false},{"label":"Upgrade Milvus by changing its image","href":"Upgrade-Milvus-by-changing-its-image","type":2,"isActive":false},{"label":"Migrate the metadata","href":"Migrate-the-metadata","type":2,"isActive":false},{"label":"What's next","href":"Whats-next","type":2,"isActive":false}]} \ No newline at end of file +{"codeList":["...\nrootcoord:\n container_name: milvus-rootcoord\n image: milvusdb/milvus:v2.4.19\n...\nproxy:\n container_name: milvus-proxy\n image: milvusdb/milvus:v2.4.19\n...\nquerycoord:\n container_name: milvus-querycoord\n image: milvusdb/milvus:v2.4.19 \n...\nquerynode:\n container_name: milvus-querynode\n image: milvusdb/milvus:v2.4.19\n...\nindexcoord:\n container_name: milvus-indexcoord\n image: milvusdb/milvus:v2.4.19\n...\nindexnode:\n container_name: milvus-indexnode\n image: milvusdb/milvus:v2.4.19 \n...\ndatacoord:\n container_name: milvus-datacoord\n image: milvusdb/milvus:v2.4.19 \n...\ndatanode:\n container_name: milvus-datanode\n image: milvusdb/milvus:v2.4.19\n","docker compose down\ndocker compose up -d\n","docker stop \n","# migration.yaml\ncmd:\n # Option: run/backup/rollback\n type: run\n runWithBackup: true\nconfig:\n sourceVersion: 2.1.4 # Specify your milvus version\n targetVersion: 2.4.19\n backupFilePath: /tmp/migration.bak\nmetastore:\n type: etcd\netcd:\n endpoints:\n - milvus-etcd:2379 # Use the etcd container name\n rootPath: by-dev # The root path where data is stored in etcd\n metaSubPath: meta\n kvSubPath: kv\n","# Suppose your docker-compose run with the default milvus network,\n# and you put migration.yaml in the same directory with docker-compose.yaml.\ndocker run --rm -it --network milvus -v $(pwd)/migration.yaml:/milvus/configs/migration.yaml milvus/meta-migration:v2.2.0 /milvus/bin/meta-migration -config=/milvus/configs/migration.yaml\n","Update the milvus image tag in the docker-compose.yaml\ndocker compose down\ndocker compose up -d\n"],"headingContent":"Upgrade Milvus Cluster with Docker Compose","anchorList":[{"label":"Upgrade Milvus Cluster with Docker Compose","href":"Upgrade-Milvus-Cluster-with-Docker-Compose","type":1,"isActive":false},{"label":"Upgrade Milvus by changing its image","href":"Upgrade-Milvus-by-changing-its-image","type":2,"isActive":false},{"label":"Migrate the metadata","href":"Migrate-the-metadata","type":2,"isActive":false},{"label":"What's next","href":"Whats-next","type":2,"isActive":false}]} \ No newline at end of file diff --git a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-docker.md b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-docker.md index bc15af7ee..1d03cfec8 100644 --- a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-docker.md +++ b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-docker.md @@ -20,7 +20,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. However, you need to migrate the metadata before any upgrade from v2.1.x to v2.4.18.

    +

    In normal cases, you can upgrade Milvus by changing its image. However, you need to migrate the metadata before any upgrade from v2.1.x to v2.4.19.

    Upgrade Milvus by changing its image

  • Run the following commands to perform the upgrade.

    docker compose down
    @@ -105,7 +105,7 @@ cmd:
       runWithBackup: true
     config:
       sourceVersion: 2.1.4   # Specify your milvus version
    -  targetVersion: 2.4.18
    +  targetVersion: 2.4.19
       backupFilePath: /tmp/migration.bak
     metastore:
       type: etcd
    diff --git a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-helm.json b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-helm.json
    index 2674e96b0..0957bb6dc 100644
    --- a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-helm.json
    +++ b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-helm.json
    @@ -1 +1 @@
    -{"codeList":["$ helm repo update zilliztech\n$ helm search repo zilliztech/milvus --versions\n","helm repo add zilliztech https://zilliztech.github.io/milvus-helm\nhelm repo update\n# upgrade existing helm release\nhelm upgrade my-release zilliztech/milvus --reset-then-reuse-values\n","NAME                    CHART VERSION   APP VERSION             DESCRIPTION                                       \nzilliztech/milvus       4.1.34          2.4.5                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.33          2.4.4                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.32          2.4.3                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.31          2.4.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.30          2.4.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.29          2.4.0                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.24          2.3.11                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.23          2.3.10                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.22          2.3.10                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.21          2.3.10                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.20          2.3.10                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.18          2.3.10                  Milvus is an open-source vector database built ... \nzilliztech/milvus       4.1.18          2.3.9                   Milvus is an open-source vector database built ...                                       \nzilliztech/milvus       4.1.17          2.3.8                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.16          2.3.7                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.15          2.3.5                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.14          2.3.6                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.13          2.3.5                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.12          2.3.5                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.11          2.3.4                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.10          2.3.3                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.9           2.3.3                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.8           2.3.2                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.7           2.3.2                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.6           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.5           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.4           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.3           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.2           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.1           2.3.0                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.0           2.3.0                   Milvus is an open-source vector database built ...\n","sh rollingUpdate.sh -n default -i my-release -o update -t 2.4.18 -w 'milvusdb/milvus:v2.4.18'\n","helm repo update zilliztech\nhelm upgrade my-release zilliztech/milvus --reset-then-reuse-values --version=4.1.24 # use the helm chart version here\n","NAME                NAMESPACE   REVISION    UPDATED                                 STATUS      CHART           APP VERSION    \nnew-release         default     1           2022-11-21 15:41:25.51539 +0800 CST     deployed    milvus-3.2.18   2.1.4 \n","NAME                                             READY   STATUS      RESTARTS   AGE\nmy-release-etcd-0                               1/1     Running     0          21m\nmy-release-etcd-1                               1/1     Running     0          21m\nmy-release-etcd-2                               1/1     Running     0          21m\nmy-release-milvus-datacoord-664c58798d-fl75s    1/1     Running     0          21m\nmy-release-milvus-datanode-5f75686c55-xfg2r     1/1     Running     0          21m\nmy-release-milvus-indexcoord-5f98b97589-2l48r   1/1     Running     0          21m\nmy-release-milvus-indexnode-857b4ddf98-vmd75    1/1     Running     0          21m\nmy-release-milvus-proxy-6c548f787f-scspp        1/1     Running     0          21m\nmy-release-milvus-querycoord-c454f44cd-dwmwq    1/1     Running     0          21m\nmy-release-milvus-querynode-76bb4946d-lbrz6     1/1     Running     0          21m\nmy-release-milvus-rootcoord-7764c5b686-62msm    1/1     Running     0          21m\nmy-release-minio-0                              1/1     Running     0          21m\nmy-release-minio-1                              1/1     Running     0          21m\nmy-release-minio-2                              1/1     Running     0          21m\nmy-release-minio-3                              1/1     Running     0          21m\nmy-release-pulsar-bookie-0                      1/1     Running     0          21m\nmy-release-pulsar-bookie-1                      1/1     Running     0          21m\nmy-release-pulsar-bookie-2                      1/1     Running     0          21m\nmy-release-pulsar-bookie-init-tjxpj             0/1     Completed   0          21m\nmy-release-pulsar-broker-0                      1/1     Running     0          21m\nmy-release-pulsar-proxy-0                       1/1     Running     0          21m\nmy-release-pulsar-pulsar-init-c8vvc             0/1     Completed   0          21m\nmy-release-pulsar-recovery-0                    1/1     Running     0          21m\nmy-release-pulsar-zookeeper-0                   1/1     Running     0          21m\nmy-release-pulsar-zookeeper-1                   1/1     Running     0          20m\nmy-release-pulsar-zookeeper-2                   1/1     Running     0          20m\n","$ kubectl get pods my-release-milvus-proxy-6c548f787f-scspp -o=jsonpath='{$.spec.containers[0].image}'\n# milvusdb/milvus:v2.1.4\n","./migrate.sh -i my-release -s 2.1.4 -t 2.2.0\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.0\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.0 -r by-dev\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.0 -r by-dev -w milvusdb/milvus:v2.2.0\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.0 -w milvusdb/milvus:v2.2.0 -d true\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.0 -r by-dev -o rollback -w milvusdb/milvus:v2.1.4\n./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.0 -r by-dev -o migrate -w milvusdb/milvus:v2.2.0\n"],"headingContent":"Upgrade Milvus Cluster with Helm Chart","anchorList":[{"label":"Upgrade Milvus Cluster with Helm Chart","href":"Upgrade-Milvus-Cluster-with-Helm-Chart","type":1,"isActive":false},{"label":"Prerequisites","href":"Prerequisites","type":2,"isActive":false},{"label":"Check Milvus Helm Chart","href":"Check-Milvus-Helm-Chart","type":2,"isActive":false},{"label":"Conduct a rolling upgrade","href":"Conduct-a-rolling-upgrade","type":2,"isActive":false},{"label":"Upgrade Milvus using Helm","href":"Upgrade-Milvus-using-Helm","type":2,"isActive":false},{"label":"Migrate the metadata","href":"Migrate-the-metadata","type":2,"isActive":false}]}
    \ No newline at end of file
    +{"codeList":["$ helm repo update zilliztech\n$ helm search repo zilliztech/milvus --versions\n","helm repo add zilliztech https://zilliztech.github.io/milvus-helm\nhelm repo update\n# upgrade existing helm release\nhelm upgrade my-release zilliztech/milvus --reset-then-reuse-values\n","NAME                    CHART VERSION   APP VERSION             DESCRIPTION                                       \nzilliztech/milvus       4.1.34          2.4.5                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.33          2.4.4                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.32          2.4.3                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.31          2.4.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.30          2.4.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.29          2.4.0                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.24          2.3.11                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.23          2.3.10                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.22          2.3.10                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.21          2.3.10                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.20          2.3.10                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.18          2.3.10                  Milvus is an open-source vector database built ... \nzilliztech/milvus       4.1.18          2.3.9                   Milvus is an open-source vector database built ...                                       \nzilliztech/milvus       4.1.17          2.3.8                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.16          2.3.7                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.15          2.3.5                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.14          2.3.6                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.13          2.3.5                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.12          2.3.5                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.11          2.3.4                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.10          2.3.3                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.9           2.3.3                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.8           2.3.2                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.7           2.3.2                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.6           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.5           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.4           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.3           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.2           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.1           2.3.0                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.0           2.3.0                   Milvus is an open-source vector database built ...\n","sh rollingUpdate.sh -n default -i my-release -o update -t 2.4.19 -w 'milvusdb/milvus:v2.4.19'\n","helm repo update zilliztech\nhelm upgrade my-release zilliztech/milvus --reset-then-reuse-values --version=4.1.24 # use the helm chart version here\n","NAME                NAMESPACE   REVISION    UPDATED                                 STATUS      CHART           APP VERSION    \nnew-release         default     1           2022-11-21 15:41:25.51539 +0800 CST     deployed    milvus-3.2.18   2.1.4 \n","NAME                                             READY   STATUS      RESTARTS   AGE\nmy-release-etcd-0                               1/1     Running     0          21m\nmy-release-etcd-1                               1/1     Running     0          21m\nmy-release-etcd-2                               1/1     Running     0          21m\nmy-release-milvus-datacoord-664c58798d-fl75s    1/1     Running     0          21m\nmy-release-milvus-datanode-5f75686c55-xfg2r     1/1     Running     0          21m\nmy-release-milvus-indexcoord-5f98b97589-2l48r   1/1     Running     0          21m\nmy-release-milvus-indexnode-857b4ddf98-vmd75    1/1     Running     0          21m\nmy-release-milvus-proxy-6c548f787f-scspp        1/1     Running     0          21m\nmy-release-milvus-querycoord-c454f44cd-dwmwq    1/1     Running     0          21m\nmy-release-milvus-querynode-76bb4946d-lbrz6     1/1     Running     0          21m\nmy-release-milvus-rootcoord-7764c5b686-62msm    1/1     Running     0          21m\nmy-release-minio-0                              1/1     Running     0          21m\nmy-release-minio-1                              1/1     Running     0          21m\nmy-release-minio-2                              1/1     Running     0          21m\nmy-release-minio-3                              1/1     Running     0          21m\nmy-release-pulsar-bookie-0                      1/1     Running     0          21m\nmy-release-pulsar-bookie-1                      1/1     Running     0          21m\nmy-release-pulsar-bookie-2                      1/1     Running     0          21m\nmy-release-pulsar-bookie-init-tjxpj             0/1     Completed   0          21m\nmy-release-pulsar-broker-0                      1/1     Running     0          21m\nmy-release-pulsar-proxy-0                       1/1     Running     0          21m\nmy-release-pulsar-pulsar-init-c8vvc             0/1     Completed   0          21m\nmy-release-pulsar-recovery-0                    1/1     Running     0          21m\nmy-release-pulsar-zookeeper-0                   1/1     Running     0          21m\nmy-release-pulsar-zookeeper-1                   1/1     Running     0          20m\nmy-release-pulsar-zookeeper-2                   1/1     Running     0          20m\n","$ kubectl get pods my-release-milvus-proxy-6c548f787f-scspp -o=jsonpath='{$.spec.containers[0].image}'\n# milvusdb/milvus:v2.1.4\n","./migrate.sh -i my-release -s 2.1.4 -t 2.2.0\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.0\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.0 -r by-dev\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.0 -r by-dev -w milvusdb/milvus:v2.2.0\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.0 -w milvusdb/milvus:v2.2.0 -d true\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.0 -r by-dev -o rollback -w milvusdb/milvus:v2.1.4\n./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.2.0 -r by-dev -o migrate -w milvusdb/milvus:v2.2.0\n"],"headingContent":"Upgrade Milvus Cluster with Helm Chart","anchorList":[{"label":"Upgrade Milvus Cluster with Helm Chart","href":"Upgrade-Milvus-Cluster-with-Helm-Chart","type":1,"isActive":false},{"label":"Prerequisites","href":"Prerequisites","type":2,"isActive":false},{"label":"Check Milvus Helm Chart","href":"Check-Milvus-Helm-Chart","type":2,"isActive":false},{"label":"Conduct a rolling upgrade","href":"Conduct-a-rolling-upgrade","type":2,"isActive":false},{"label":"Upgrade Milvus using Helm","href":"Upgrade-Milvus-using-Helm","type":2,"isActive":false},{"label":"Migrate the metadata","href":"Migrate-the-metadata","type":2,"isActive":false}]}
    \ No newline at end of file
    diff --git a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md
    index 70cd478aa..0662883f6 100644
    --- a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md
    +++ b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md
    @@ -108,10 +108,10 @@ zilliztech/milvus       4.1.1           2.3.0                   Milvus is an ope
     zilliztech/milvus       4.1.0           2.3.0                   Milvus is an open-source vector database built ...
     

    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.18.
    +
    - [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.4.19.

    Conduct a rolling upgrade
      diff --git a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-operator.json b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-operator.json index e8a855ac4..8a622abd4 100644 --- a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-operator.json +++ b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-operator.json @@ -1 +1 @@ -{"codeList":["helm repo add zilliztech-milvus-operator https://zilliztech.github.io/milvus-operator/\nhelm repo update zilliztech-milvus-operator\nhelm -n milvus-operator upgrade milvus-operator zilliztech-milvus-operator/milvus-operator\n","apiVersion: milvus.io/v1beta1\nkind: Milvus\nmetadata:\n name: my-release\nspec:\n components:\n enableRollingUpdate: true\n imageUpdateMode: rollingUpgrade # Default value, can be omitted\n image: milvusdb/milvus:v2.4.18\n","apiVersion: milvus.io/v1beta1\nkind: Milvus\nmetadata:\n name: my-release\nspec:\n components:\n enableRollingUpdate: true\n imageUpdateMode: all\n image: milvusdb/milvus:v2.4.18\n","apiVersion: milvus.io/v1beta1\nkind: Milvus\nmetadata:\n name: my-release\nspec:\n components:\n enableRollingUpdate: true\n imageUpdateMode: rollingDowngrade\n image: milvusdb/milvus:\n","kubectl patch -f milvusupgrade.yml\n","apiVersion: milvus.io/v1beta1\nkind: Milvus\nmetadata:\n name: my-release\nspec:\n # Omit other fields ...\n components:\n image: milvusdb/milvus:v2.4.18\n","kubectl patch -f milvusupgrade.yaml\n","apiVersion: milvus.io/v1beta1\nkind: MilvusUpgrade\nmetadata:\n name: my-release-upgrade\nspec:\n milvus:\n namespace: default\n name: my-release\n sourceVersion: \"v2.1.4\"\n targetVersion: \"v2.4.18\"\n # below are some omit default values:\n # targetImage: \"milvusdb/milvus:v2.4.18\"\n # toolImage: \"milvusdb/meta-migration:v2.2.0\"\n # operation: upgrade\n # rollbackIfFailed: true\n # backupPVC: \"\"\n # maxRetry: 3\n","$ kubectl create -f https://github.com/zilliztech/milvus-operator/blob/main/config/samples/beta/milvusupgrade.yaml\n","kubectl describe milvus release-name\n"],"headingContent":"Upgrade Milvus Cluster with Milvus Operator","anchorList":[{"label":"Upgrade Milvus Cluster with Milvus Operator","href":"Upgrade-Milvus-Cluster-with-Milvus-Operator","type":1,"isActive":false},{"label":"Upgrade your Milvus operator","href":"Upgrade-your-Milvus-operator","type":2,"isActive":false},{"label":"Conduct a rolling upgrade","href":"Conduct-a-rolling-upgrade","type":2,"isActive":false},{"label":"Upgrade Milvus by changing its image","href":"Upgrade-Milvus-by-changing-its-image","type":2,"isActive":false},{"label":"Migrate the metadata","href":"Migrate-the-metadata","type":2,"isActive":false}]} \ No newline at end of file +{"codeList":["helm repo add zilliztech-milvus-operator https://zilliztech.github.io/milvus-operator/\nhelm repo update zilliztech-milvus-operator\nhelm -n milvus-operator upgrade milvus-operator zilliztech-milvus-operator/milvus-operator\n","apiVersion: milvus.io/v1beta1\nkind: Milvus\nmetadata:\n name: my-release\nspec:\n components:\n enableRollingUpdate: true\n imageUpdateMode: rollingUpgrade # Default value, can be omitted\n image: milvusdb/milvus:v2.4.19\n","apiVersion: milvus.io/v1beta1\nkind: Milvus\nmetadata:\n name: my-release\nspec:\n components:\n enableRollingUpdate: true\n imageUpdateMode: all\n image: milvusdb/milvus:v2.4.19\n","apiVersion: milvus.io/v1beta1\nkind: Milvus\nmetadata:\n name: my-release\nspec:\n components:\n enableRollingUpdate: true\n imageUpdateMode: rollingDowngrade\n image: milvusdb/milvus:\n","kubectl patch -f milvusupgrade.yml\n","apiVersion: milvus.io/v1beta1\nkind: Milvus\nmetadata:\n name: my-release\nspec:\n # Omit other fields ...\n components:\n image: milvusdb/milvus:v2.4.19\n","kubectl patch -f milvusupgrade.yaml\n","apiVersion: milvus.io/v1beta1\nkind: MilvusUpgrade\nmetadata:\n name: my-release-upgrade\nspec:\n milvus:\n namespace: default\n name: my-release\n sourceVersion: \"v2.1.4\"\n targetVersion: \"v2.4.19\"\n # below are some omit default values:\n # targetImage: \"milvusdb/milvus:v2.4.19\"\n # toolImage: \"milvusdb/meta-migration:v2.2.0\"\n # operation: upgrade\n # rollbackIfFailed: true\n # backupPVC: \"\"\n # maxRetry: 3\n","$ kubectl create -f https://github.com/zilliztech/milvus-operator/blob/main/config/samples/beta/milvusupgrade.yaml\n","kubectl describe milvus release-name\n"],"headingContent":"Upgrade Milvus Cluster with Milvus Operator","anchorList":[{"label":"Upgrade Milvus Cluster with Milvus Operator","href":"Upgrade-Milvus-Cluster-with-Milvus-Operator","type":1,"isActive":false},{"label":"Upgrade your Milvus operator","href":"Upgrade-your-Milvus-operator","type":2,"isActive":false},{"label":"Conduct a rolling upgrade","href":"Conduct-a-rolling-upgrade","type":2,"isActive":false},{"label":"Upgrade Milvus by changing its image","href":"Upgrade-Milvus-by-changing-its-image","type":2,"isActive":false},{"label":"Migrate the metadata","href":"Migrate-the-metadata","type":2,"isActive":false}]} \ No newline at end of file diff --git a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-operator.md b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-operator.md index 3656a88d7..01900dbd5 100644 --- a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-operator.md +++ b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_cluster-operator.md @@ -46,9 +46,9 @@ helm -n milvus-operator upgrade milvus-

      Once you have upgraded your Milvus operator to the latest version, you have the following choices:

      Conduct a rolling upgrade

      In this above configuration file, set spec.components.enableRollingUpdate to true and set spec.components.image to the desired Milvus version.

      By default, Milvus performs rolling upgrade for coordinators in an ordered way, in which it replaces the coordinator pod images one after another. To reduce the upgrade time, consider setting spec.components.imageUpdateMode to all so that Milvus replaces all pod images at the same time.

      @@ -88,7 +88,7 @@ spec: components: enableRollingUpdate: true imageUpdateMode: all - image: milvusdb/milvus:v2.4.18 + image: milvusdb/milvus:v2.4.19

      You can set spec.components.imageUpdateMode to rollingDowngrade to have Milvus replace coordinator pod images with a lower version.

      apiVersion: milvus.io/v1beta1
      @@ -128,7 +128,7 @@ metadata:
       spec:
         # Omit other fields ...
         components:
      -   image: milvusdb/milvus:v2.4.18
      +   image: milvusdb/milvus:v2.4.19
       

      Then run the following to perform the upgrade:

      kubectl patch -f milvusupgrade.yaml
      @@ -148,8 +148,8 @@ spec:
                 d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"
               >
             
      -    

      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.18.

      -

      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.18. This means that your Milvus cluster will be upgraded from v2.1.4 to v2.4.18.

      +

    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.19.

    +

    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.19. This means that your Milvus cluster will be upgraded from v2.1.4 to v2.4.19.

    apiVersion: milvus.io/v1beta1
     kind: MilvusUpgrade
     metadata:
    @@ -159,9 +159,9 @@ spec:
         namespace: default
         name: my-release
       sourceVersion: "v2.1.4"
    -  targetVersion: "v2.4.18"
    +  targetVersion: "v2.4.19"
       # below are some omit default values:
    -  # targetImage: "milvusdb/milvus:v2.4.18"
    +  # targetImage: "milvusdb/milvus:v2.4.19"
       # toolImage: "milvusdb/meta-migration:v2.2.0"
       # operation: upgrade
       # rollbackIfFailed: true
    diff --git a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-docker.json b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-docker.json
    index 0136fbea1..9ec4dc444 100644
    --- a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-docker.json
    +++ b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-docker.json
    @@ -1 +1 @@
    -{"codeList":["...\nstandalone:\n  container_name: milvus-standalone\n  image: milvusdb/milvus:v2.4.18\n","docker compose down\ndocker compose up -d\n","docker stop \n","# migration.yaml\ncmd:\n  # Option: run/backup/rollback\n  type: run\n  runWithBackup: true\nconfig:\n  sourceVersion: 2.1.4   # Specify your milvus version\n  targetVersion: 2.4.18\n  backupFilePath: /tmp/migration.bak\nmetastore:\n  type: etcd\netcd:\n  endpoints:\n    - milvus-etcd:2379  # Use the etcd container name\n  rootPath: by-dev # The root path where data is stored in etcd\n  metaSubPath: meta\n  kvSubPath: kv\n","# Suppose your docker-compose run with the default milvus network,\n# and you put migration.yaml in the same directory with docker-compose.yaml.\ndocker run --rm -it --network milvus -v $(pwd)/migration.yaml:/milvus/configs/migration.yaml milvusdb/meta-migration:v2.2.0 /milvus/bin/meta-migration -config=/milvus/configs/migration.yaml\n","// Run the following only after update the milvus image tag in the docker-compose.yaml\ndocker compose down\ndocker compose up -d\n"],"headingContent":"Upgrade Milvus Standalone with Docker Compose","anchorList":[{"label":"Upgrade Milvus Standalone with Docker Compose","href":"Upgrade-Milvus-Standalone-with-Docker-Compose","type":1,"isActive":false},{"label":"Upgrade Milvus by changing its image","href":"Upgrade-Milvus-by-changing-its-image","type":2,"isActive":false},{"label":"Migrate the metadata","href":"Migrate-the-metadata","type":2,"isActive":false},{"label":"What's next","href":"Whats-next","type":2,"isActive":false}]}
    \ No newline at end of file
    +{"codeList":["...\nstandalone:\n  container_name: milvus-standalone\n  image: milvusdb/milvus:v2.4.19\n","docker compose down\ndocker compose up -d\n","docker stop \n","# migration.yaml\ncmd:\n  # Option: run/backup/rollback\n  type: run\n  runWithBackup: true\nconfig:\n  sourceVersion: 2.1.4   # Specify your milvus version\n  targetVersion: 2.4.19\n  backupFilePath: /tmp/migration.bak\nmetastore:\n  type: etcd\netcd:\n  endpoints:\n    - milvus-etcd:2379  # Use the etcd container name\n  rootPath: by-dev # The root path where data is stored in etcd\n  metaSubPath: meta\n  kvSubPath: kv\n","# Suppose your docker-compose run with the default milvus network,\n# and you put migration.yaml in the same directory with docker-compose.yaml.\ndocker run --rm -it --network milvus -v $(pwd)/migration.yaml:/milvus/configs/migration.yaml milvusdb/meta-migration:v2.2.0 /milvus/bin/meta-migration -config=/milvus/configs/migration.yaml\n","// Run the following only after update the milvus image tag in the docker-compose.yaml\ndocker compose down\ndocker compose up -d\n"],"headingContent":"Upgrade Milvus Standalone with Docker Compose","anchorList":[{"label":"Upgrade Milvus Standalone with Docker Compose","href":"Upgrade-Milvus-Standalone-with-Docker-Compose","type":1,"isActive":false},{"label":"Upgrade Milvus by changing its image","href":"Upgrade-Milvus-by-changing-its-image","type":2,"isActive":false},{"label":"Migrate the metadata","href":"Migrate-the-metadata","type":2,"isActive":false},{"label":"What's next","href":"Whats-next","type":2,"isActive":false}]}
    \ No newline at end of file
    diff --git a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-docker.md b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-docker.md
    index 6b476b59f..0fd94dbd6 100644
    --- a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-docker.md
    +++ b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-docker.md
    @@ -24,7 +24,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. However, you need to migrate the metadata before any upgrade from v2.1.x to v2.4.18.

    +

    In normal cases, you can upgrade Milvus by changing its image. However, you need to migrate the metadata before any upgrade from v2.1.x to v2.4.19.

    Due to security concerns, Milvus upgrades its MinIO to RELEASE.2023-03-20T20-16-18Z with the release of v2.2.5. Before any upgrades from previous Milvus Standalone releases installed using Docker Compose, you should create a Single-Node Single-Drive MinIO deployment and migrate existing MinIO settings and content to the new deployment. For details, refer to this guide.

    @@ -49,7 +49,7 @@ title: Upgrade Milvus Standalone with Docker Compose
    ...
     standalone:
       container_name: milvus-standalone
    -  image: milvusdb/milvus:v2.4.18
    +  image: milvusdb/milvus:v2.4.19
     
  • Run the following commands to perform the upgrade.

    docker compose down
    @@ -83,7 +83,7 @@ cmd:
       runWithBackup: true
     config:
       sourceVersion: 2.1.4   # Specify your milvus version
    -  targetVersion: 2.4.18
    +  targetVersion: 2.4.19
       backupFilePath: /tmp/migration.bak
     metastore:
       type: etcd
    diff --git a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-helm.json b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-helm.json
    index 43b2985c3..310f7ae43 100644
    --- a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-helm.json
    +++ b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-helm.json
    @@ -1 +1 @@
    -{"codeList":["$ helm repo update\n$ helm search repo zilliztech/milvus --versions\n","helm repo add zilliztech https://zilliztech.github.io/milvus-helm\nhelm repo update zilliztech\n# upgrade existing helm release\nhelm upgrade my-release zilliztech/milvus --reset-then-reuse-values\n","NAME                    CHART VERSION   APP VERSION             DESCRIPTION                                       \nzilliztech/milvus       4.1.34          2.4.5                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.33          2.4.4                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.32          2.4.3                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.31          2.4.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.30          2.4.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.29          2.4.0                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.24          2.3.11                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.23          2.3.10                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.22          2.3.10                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.21          2.3.10                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.20          2.3.10                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.18          2.3.10                  Milvus is an open-source vector database built ... \nzilliztech/milvus       4.1.18          2.3.9                   Milvus is an open-source vector database built ...                                       \nzilliztech/milvus       4.1.17          2.3.8                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.16          2.3.7                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.15          2.3.5                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.14          2.3.6                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.13          2.3.5                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.12          2.3.5                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.11          2.3.4                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.10          2.3.3                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.9           2.3.3                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.8           2.3.2                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.7           2.3.2                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.6           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.5           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.4           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.3           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.2           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.1           2.3.0                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.0           2.3.0                   Milvus is an open-source vector database built ...\n","sh rollingUpdate.sh -n default -i my-release -o update -t 2.4.18 -w 'milvusdb/milvus:v2.4.18'\n","helm repo update\nhelm upgrade my-release milvus/milvus --reset-then-reuse-values --version=4.1.24 # use the helm chart version here\n","NAME                NAMESPACE   REVISION    UPDATED                                 STATUS      CHART           APP VERSION     \nmy-release          default     1           2022-11-21 15:41:25.51539 +0800 CST     deployed    milvus-3.2.18   2.1.4\n","NAME                                            READY   STATUS    RESTARTS   AGE\nmy-release-etcd-0                               1/1     Running   0          84s\nmy-release-milvus-standalone-75c599fffc-6rwlj   1/1     Running   0          84s\nmy-release-minio-744dd9586f-qngzv               1/1     Running   0          84s\n","$ kubectl get pods my-release-milvus-proxy-6c548f787f-scspp -o=jsonpath='{$.spec.containers[0].image}'\n# milvusdb/milvus:v2.1.4\n","./migrate.sh -i my-release -s 2.1.4 -t 2.4.18\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.18\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.18 -r by-dev\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.18 -r by-dev -w milvusdb/milvus:v2.4.18\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.18 -w milvusdb/milvus:v2.4.18 -d true\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.18 -r by-dev -o rollback -w milvusdb/milvus:v2.1.1\n./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.18 -r by-dev -o migrate -w milvusdb/milvus:v2.4.18\n"],"headingContent":"Upgrade Milvus Standalone with Helm Chart","anchorList":[{"label":"Upgrade Milvus Standalone with Helm Chart","href":"Upgrade-Milvus-Standalone-with-Helm-Chart","type":1,"isActive":false},{"label":"Prerequisites","href":"Prerequisites","type":2,"isActive":false},{"label":"Check the Milvus version","href":"Check-the-Milvus-version","type":2,"isActive":false},{"label":"Conduct a rolling upgrade","href":"Conduct-a-rolling-upgrade","type":2,"isActive":false},{"label":"Upgrade Milvus using Helm","href":"Upgrade-Milvus-using-Helm","type":2,"isActive":false},{"label":"Migrate the metadata","href":"Migrate-the-metadata","type":2,"isActive":false}]}
    \ No newline at end of file
    +{"codeList":["$ helm repo update\n$ helm search repo zilliztech/milvus --versions\n","helm repo add zilliztech https://zilliztech.github.io/milvus-helm\nhelm repo update zilliztech\n# upgrade existing helm release\nhelm upgrade my-release zilliztech/milvus --reset-then-reuse-values\n","NAME                    CHART VERSION   APP VERSION             DESCRIPTION                                       \nzilliztech/milvus       4.1.34          2.4.5                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.33          2.4.4                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.32          2.4.3                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.31          2.4.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.30          2.4.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.29          2.4.0                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.24          2.3.11                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.23          2.3.10                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.22          2.3.10                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.21          2.3.10                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.20          2.3.10                  Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.18          2.3.10                  Milvus is an open-source vector database built ... \nzilliztech/milvus       4.1.18          2.3.9                   Milvus is an open-source vector database built ...                                       \nzilliztech/milvus       4.1.17          2.3.8                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.16          2.3.7                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.15          2.3.5                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.14          2.3.6                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.13          2.3.5                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.12          2.3.5                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.11          2.3.4                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.10          2.3.3                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.9           2.3.3                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.8           2.3.2                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.7           2.3.2                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.6           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.5           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.4           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.3           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.2           2.3.1                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.1           2.3.0                   Milvus is an open-source vector database built ...\nzilliztech/milvus       4.1.0           2.3.0                   Milvus is an open-source vector database built ...\n","sh rollingUpdate.sh -n default -i my-release -o update -t 2.4.19 -w 'milvusdb/milvus:v2.4.19'\n","helm repo update\nhelm upgrade my-release milvus/milvus --reset-then-reuse-values --version=4.1.24 # use the helm chart version here\n","NAME                NAMESPACE   REVISION    UPDATED                                 STATUS      CHART           APP VERSION     \nmy-release          default     1           2022-11-21 15:41:25.51539 +0800 CST     deployed    milvus-3.2.18   2.1.4\n","NAME                                            READY   STATUS    RESTARTS   AGE\nmy-release-etcd-0                               1/1     Running   0          84s\nmy-release-milvus-standalone-75c599fffc-6rwlj   1/1     Running   0          84s\nmy-release-minio-744dd9586f-qngzv               1/1     Running   0          84s\n","$ kubectl get pods my-release-milvus-proxy-6c548f787f-scspp -o=jsonpath='{$.spec.containers[0].image}'\n# milvusdb/milvus:v2.1.4\n","./migrate.sh -i my-release -s 2.1.4 -t 2.4.19\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.19\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.19 -r by-dev\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.19 -r by-dev -w milvusdb/milvus:v2.4.19\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.19 -w milvusdb/milvus:v2.4.19 -d true\n","./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.19 -r by-dev -o rollback -w milvusdb/milvus:v2.1.1\n./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.19 -r by-dev -o migrate -w milvusdb/milvus:v2.4.19\n"],"headingContent":"Upgrade Milvus Standalone with Helm Chart","anchorList":[{"label":"Upgrade Milvus Standalone with Helm Chart","href":"Upgrade-Milvus-Standalone-with-Helm-Chart","type":1,"isActive":false},{"label":"Prerequisites","href":"Prerequisites","type":2,"isActive":false},{"label":"Check the Milvus version","href":"Check-the-Milvus-version","type":2,"isActive":false},{"label":"Conduct a rolling upgrade","href":"Conduct-a-rolling-upgrade","type":2,"isActive":false},{"label":"Upgrade Milvus using Helm","href":"Upgrade-Milvus-using-Helm","type":2,"isActive":false},{"label":"Migrate the metadata","href":"Migrate-the-metadata","type":2,"isActive":false}]}
    \ No newline at end of file
    diff --git a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md
    index a9df91560..d59010fa2 100644
    --- a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md
    +++ b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md
    @@ -108,10 +108,10 @@ zilliztech/milvus       4.1.1           2.3.0                   Milvus is an ope
     zilliztech/milvus       4.1.0           2.3.0                   Milvus is an open-source vector database built ...
     

    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.18.
    +
    - [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.4.19.

    Conduct a rolling upgrade
      @@ -235,25 +235,25 @@ my-release-minio-744dd9586f-qngzv 1/1 Running 0 84s
    1. Migrate the Milvus metadata.
    2. Start Milvus components with a new image.
    -

    2. Upgrade Milvus from v2.1.x to 2.4.18

    The following commands assume that you upgrade Milvus from v2.1.4 to 2.4.18. Change them to the versions that fit your needs.

    +

    2. Upgrade Milvus from v2.1.x to 2.4.19

    The following commands assume that you upgrade Milvus from v2.1.4 to 2.4.19. 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.18
      +
      ./migrate.sh -i my-release -s 2.1.4 -t 2.4.19
       
    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.18
      +
      ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.19
       
    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.18 -r by-dev
      +
      ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.19 -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.18 -r by-dev -w milvusdb/milvus:v2.4.18
      +
      ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.19 -r by-dev -w milvusdb/milvus:v2.4.19
       
    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.18 -w milvusdb/milvus:v2.4.18 -d true
      +
      ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.19 -w milvusdb/milvus:v2.4.19 -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.18 -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.18 -r by-dev -o migrate -w milvusdb/milvus:v2.4.18
      +
      ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.4.19 -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.19 -r by-dev -o migrate -w milvusdb/milvus:v2.4.19
       
    diff --git a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-operator.json b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-operator.json index d5108aa66..2dc8af95d 100644 --- a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-operator.json +++ b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-operator.json @@ -1 +1 @@ -{"codeList":["helm repo add zilliztech-milvus-operator https://zilliztech.github.io/milvus-operator/\nhelm repo update zilliztech-milvus-operator\nhelm -n milvus-operator upgrade milvus-operator zilliztech-milvus-operator/milvus-operator\n","apiVersion: milvus.io/v1beta1\nkind: Milvus\nmetadata:\n name: my-release\nspec:\n components:\n enableRollingUpdate: true\n imageUpdateMode: rollingUpgrade # Default value, can be omitted\n image: milvusdb/milvus:v2.4.18\n","apiVersion: milvus.io/v1beta1\nkind: Milvus\nmetadata:\n name: my-release\nspec:\n components:\n enableRollingUpdate: true\n imageUpdateMode: all\n image: milvusdb/milvus:v2.4.18\n","apiVersion: milvus.io/v1beta1\nkind: Milvus\nmetadata:\n name: my-release\nspec:\n components:\n enableRollingUpdate: true\n imageUpdateMode: rollingDowngrade\n image: milvusdb/milvus:\n","kubectl patch -f milvusupgrade.yml\n","apiVersion: milvus.io/v1beta1\nkind: Milvus\nmetadata:\n name: my-release\nlabels:\n app: milvus\nspec:\n # Omit other fields ...\n components:\n image: milvusdb/milvus:v2.4.18\n","kubectl patch -f milvusupgrade.yaml\n","apiVersion: milvus.io/v1beta1\nkind: MilvusUpgrade\nmetadata:\n name: my-release-upgrade\nspec:\n milvus:\n namespace: default\n name: my-release\n sourceVersion: \"v2.1.4\"\n targetVersion: \"v2.4.18\"\n # below are some omit default values:\n # targetImage: \"milvusdb/milvus:v2.4.18\"\n # toolImage: \"milvusdb/meta-migration:v2.2.0\"\n # operation: upgrade\n # rollbackIfFailed: true\n # backupPVC: \"\"\n # maxRetry: 3\n","$ kubectl create -f https://raw.githubusercontent.com/zilliztech/milvus-operator/main/config/samples/milvusupgrade.yaml\n","kubectl describe milvus release-name\n"],"headingContent":"Upgrade Milvus Standalone with Milvus Operator","anchorList":[{"label":"Upgrade Milvus Standalone with Milvus Operator","href":"Upgrade-Milvus-Standalone-with-Milvus-Operator","type":1,"isActive":false},{"label":"Upgrade your Milvus operator","href":"Upgrade-your-Milvus-operator","type":2,"isActive":false},{"label":"Conduct a rolling upgrade","href":"Conduct-a-rolling-upgrade","type":2,"isActive":false},{"label":"Upgrade Milvus by changing its image","href":"Upgrade-Milvus-by-changing-its-image","type":2,"isActive":false},{"label":"Migrate the metadata","href":"Migrate-the-metadata","type":2,"isActive":false}]} \ No newline at end of file +{"codeList":["helm repo add zilliztech-milvus-operator https://zilliztech.github.io/milvus-operator/\nhelm repo update zilliztech-milvus-operator\nhelm -n milvus-operator upgrade milvus-operator zilliztech-milvus-operator/milvus-operator\n","apiVersion: milvus.io/v1beta1\nkind: Milvus\nmetadata:\n name: my-release\nspec:\n components:\n enableRollingUpdate: true\n imageUpdateMode: rollingUpgrade # Default value, can be omitted\n image: milvusdb/milvus:v2.4.19\n","apiVersion: milvus.io/v1beta1\nkind: Milvus\nmetadata:\n name: my-release\nspec:\n components:\n enableRollingUpdate: true\n imageUpdateMode: all\n image: milvusdb/milvus:v2.4.19\n","apiVersion: milvus.io/v1beta1\nkind: Milvus\nmetadata:\n name: my-release\nspec:\n components:\n enableRollingUpdate: true\n imageUpdateMode: rollingDowngrade\n image: milvusdb/milvus:\n","kubectl patch -f milvusupgrade.yml\n","apiVersion: milvus.io/v1beta1\nkind: Milvus\nmetadata:\n name: my-release\nlabels:\n app: milvus\nspec:\n # Omit other fields ...\n components:\n image: milvusdb/milvus:v2.4.19\n","kubectl patch -f milvusupgrade.yaml\n","apiVersion: milvus.io/v1beta1\nkind: MilvusUpgrade\nmetadata:\n name: my-release-upgrade\nspec:\n milvus:\n namespace: default\n name: my-release\n sourceVersion: \"v2.1.4\"\n targetVersion: \"v2.4.19\"\n # below are some omit default values:\n # targetImage: \"milvusdb/milvus:v2.4.19\"\n # toolImage: \"milvusdb/meta-migration:v2.2.0\"\n # operation: upgrade\n # rollbackIfFailed: true\n # backupPVC: \"\"\n # maxRetry: 3\n","$ kubectl create -f https://raw.githubusercontent.com/zilliztech/milvus-operator/main/config/samples/milvusupgrade.yaml\n","kubectl describe milvus release-name\n"],"headingContent":"Upgrade Milvus Standalone with Milvus Operator","anchorList":[{"label":"Upgrade Milvus Standalone with Milvus Operator","href":"Upgrade-Milvus-Standalone-with-Milvus-Operator","type":1,"isActive":false},{"label":"Upgrade your Milvus operator","href":"Upgrade-your-Milvus-operator","type":2,"isActive":false},{"label":"Conduct a rolling upgrade","href":"Conduct-a-rolling-upgrade","type":2,"isActive":false},{"label":"Upgrade Milvus by changing its image","href":"Upgrade-Milvus-by-changing-its-image","type":2,"isActive":false},{"label":"Migrate the metadata","href":"Migrate-the-metadata","type":2,"isActive":false}]} \ No newline at end of file diff --git a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-operator.md b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-operator.md index 7fa47d59f..91e59deda 100644 --- a/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-operator.md +++ b/localization/v2.4.x/site/en/adminGuide/upgrade_milvus_standalone-operator.md @@ -46,9 +46,9 @@ helm -n milvus-operator upgrade milvus-

    Once you have upgraded your Milvus operator to the latest version, you have the following choices:

    Conduct a rolling upgrade

    In this above configuration file, set spec.components.enableRollingUpdate to true and set spec.components.image to the desired Milvus version.

    By default, Milvus performs a rolling upgrade for coordinators in an ordered way, in which it replaces the coordinator pod images one after another. To reduce the upgrade time, consider setting spec.components.imageUpdateMode to all so that Milvus replaces all pod images at the same time.

    @@ -88,7 +88,7 @@ spec: components: enableRollingUpdate: true imageUpdateMode: all - image: milvusdb/milvus:v2.4.18 + image: milvusdb/milvus:v2.4.19

    You can set spec.components.imageUpdateMode to rollingDowngrade to have Milvus replace coordinator pod images with a lower version.

    apiVersion: milvus.io/v1beta1
    @@ -130,7 +130,7 @@ labels:
     spec:
       # Omit other fields ...
       components:
    -   image: milvusdb/milvus:v2.4.18
    +   image: milvusdb/milvus:v2.4.19
     

    Then run the following to perform the upgrade:

    kubectl patch -f milvusupgrade.yaml
    @@ -150,8 +150,8 @@ spec:
               d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"
             >
           
    -    

    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.18.

    -

    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.18. This means that your Milvus instance will be upgraded from v2.1.4 to v2.4.18.

    +

    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.19.

    +

    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.19. This means that your Milvus instance will be upgraded from v2.1.4 to v2.4.19.

    apiVersion: milvus.io/v1beta1
     kind: MilvusUpgrade
     metadata:
    @@ -161,9 +161,9 @@ spec:
         namespace: default
         name: my-release
       sourceVersion: "v2.1.4"
    -  targetVersion: "v2.4.18"
    +  targetVersion: "v2.4.19"
       # below are some omit default values:
    -  # targetImage: "milvusdb/milvus:v2.4.18"
    +  # targetImage: "milvusdb/milvus:v2.4.19"
       # toolImage: "milvusdb/meta-migration:v2.2.0"
       # operation: upgrade
       # rollbackIfFailed: true
    diff --git a/localization/v2.4.x/site/en/getstarted/install_SDKs/install-pymilvus.json b/localization/v2.4.x/site/en/getstarted/install_SDKs/install-pymilvus.json
    index f3ca4c457..7b9a7896c 100644
    --- a/localization/v2.4.x/site/en/getstarted/install_SDKs/install-pymilvus.json
    +++ b/localization/v2.4.x/site/en/getstarted/install_SDKs/install-pymilvus.json
    @@ -1 +1 @@
    -{"codeList":["$ python3 -m pip install pymilvus==2.4.9\n","$ python3 -c \"from pymilvus import Collection\"\n"],"headingContent":"Install Milvus Python SDK","anchorList":[{"label":"Install Milvus Python SDK","href":"Install-Milvus-Python-SDK","type":1,"isActive":false},{"label":"Requirements","href":"Requirements","type":2,"isActive":false},{"label":"Install PyMilvus via pip","href":"Install-PyMilvus-via-pip","type":2,"isActive":false},{"label":"Verify installation","href":"Verify-installation","type":2,"isActive":false},{"label":"What's next","href":"Whats-next","type":2,"isActive":false}]}
    \ No newline at end of file
    +{"codeList":["$ python3 -m pip install pymilvus==2.4.13\n","$ python3 -c \"from pymilvus import Collection\"\n"],"headingContent":"Install Milvus Python SDK","anchorList":[{"label":"Install Milvus Python SDK","href":"Install-Milvus-Python-SDK","type":1,"isActive":false},{"label":"Requirements","href":"Requirements","type":2,"isActive":false},{"label":"Install PyMilvus via pip","href":"Install-PyMilvus-via-pip","type":2,"isActive":false},{"label":"Verify installation","href":"Verify-installation","type":2,"isActive":false},{"label":"What's next","href":"Whats-next","type":2,"isActive":false}]}
    \ No newline at end of file
    diff --git a/localization/v2.4.x/site/en/getstarted/install_SDKs/install-pymilvus.md b/localization/v2.4.x/site/en/getstarted/install_SDKs/install-pymilvus.md
    index 631c75772..1d7f07865 100644
    --- a/localization/v2.4.x/site/en/getstarted/install_SDKs/install-pymilvus.md
    +++ b/localization/v2.4.x/site/en/getstarted/install_SDKs/install-pymilvus.md
    @@ -61,7 +61,7 @@ title: Install Milvus Python SDK
     
    It is recommended to install a PyMilvus version that matches the version of the Milvus server you installed. For more information, see Release Notes.
    -
    $ python3 -m pip install pymilvus==2.4.9
    +
    $ python3 -m pip install pymilvus==2.4.13
     

    Verify installation

    Milvus provides a Docker Compose configuration file in the Milvus repository. To install Milvus using Docker Compose, just run

    # Download the configuration file
    -$ wget https://github.com/milvus-io/milvus/releases/download/v2.4.18/milvus-standalone-docker-compose.yml -O docker-compose.yml
    +$ wget https://github.com/milvus-io/milvus/releases/download/v2.4.19/milvus-standalone-docker-compose.yml -O docker-compose.yml
     
     # Start Milvus
     $ sudo docker compose up -d
    diff --git a/localization/v2.4.x/site/en/getstarted/run-milvus-gpu/install_standalone-docker-compose-gpu.json b/localization/v2.4.x/site/en/getstarted/run-milvus-gpu/install_standalone-docker-compose-gpu.json
    index f00918d30..6f5b13ee6 100644
    --- a/localization/v2.4.x/site/en/getstarted/run-milvus-gpu/install_standalone-docker-compose-gpu.json
    +++ b/localization/v2.4.x/site/en/getstarted/run-milvus-gpu/install_standalone-docker-compose-gpu.json
    @@ -1 +1 @@
    -{"codeList":["$ wget https://github.com/milvus-io/milvus/releases/download/v2.4.18/milvus-standalone-docker-compose-gpu.yml -O docker-compose.yml\n","...\nstandalone:\n  ...\n  deploy:\n    resources:\n      reservations:\n        devices:\n          - driver: nvidia\n            capabilities: [\"gpu\"]\n            device_ids: [\"0\"]\n...\n","...\nstandalone:\n  ...\n  deploy:\n    resources:\n      reservations:\n        devices:\n          - driver: nvidia\n            capabilities: [\"gpu\"]\n            device_ids: ['0', '1']\n...\n","$ sudo docker compose up -d\n\nCreating milvus-etcd  ... done\nCreating milvus-minio ... done\nCreating milvus-standalone ... done\n","$ sudo docker compose ps\n\n      Name                     Command                  State                            Ports\n--------------------------------------------------------------------------------------------------------------------\nmilvus-etcd         etcd -advertise-client-url ...   Up             2379/tcp, 2380/tcp\nmilvus-minio        /usr/bin/docker-entrypoint ...   Up (healthy)   9000/tcp\nmilvus-standalone   /tini -- milvus run standalone   Up             0.0.0.0:19530->19530/tcp, 0.0.0.0:9091->9091/tcp\n","$ CUDA_VISIBLE_DEVICES=0 ./milvus run standalone\n","$ CUDA_VISIBLE_DEVICES=0,1 ./milvus run standalone\n","# Stop Milvus\n$ sudo docker compose down\n\n# Delete service data\n$ sudo rm -rf volumes\n","docker cp :/milvus/configs/milvus.yaml milvus.yaml\n","vim milvus.yaml\n","...\ngpu:\n  initMemSize: 0\n  maxMemSize: 0\n...\n","docker cp milvus.yaml :/milvus/configs/milvus.yaml\n","docker stop \ndocker start \n"],"headingContent":"Run Milvus with GPU Support Using Docker Compose","anchorList":[{"label":"Run Milvus with GPU Support Using Docker Compose","href":"Run-Milvus-with-GPU-Support-Using-Docker-Compose","type":1,"isActive":false},{"label":"Prerequisites","href":"Prerequisites","type":2,"isActive":false},{"label":"Install Milvus","href":"Install-Milvus","type":2,"isActive":false},{"label":"Configure memory pool","href":"Configure-memory-pool","type":2,"isActive":false},{"label":"What's next","href":"Whats-next","type":2,"isActive":false}]}
    \ No newline at end of file
    +{"codeList":["$ wget https://github.com/milvus-io/milvus/releases/download/v2.4.19/milvus-standalone-docker-compose-gpu.yml -O docker-compose.yml\n","...\nstandalone:\n  ...\n  deploy:\n    resources:\n      reservations:\n        devices:\n          - driver: nvidia\n            capabilities: [\"gpu\"]\n            device_ids: [\"0\"]\n...\n","...\nstandalone:\n  ...\n  deploy:\n    resources:\n      reservations:\n        devices:\n          - driver: nvidia\n            capabilities: [\"gpu\"]\n            device_ids: ['0', '1']\n...\n","$ sudo docker compose up -d\n\nCreating milvus-etcd  ... done\nCreating milvus-minio ... done\nCreating milvus-standalone ... done\n","$ sudo docker compose ps\n\n      Name                     Command                  State                            Ports\n--------------------------------------------------------------------------------------------------------------------\nmilvus-etcd         etcd -advertise-client-url ...   Up             2379/tcp, 2380/tcp\nmilvus-minio        /usr/bin/docker-entrypoint ...   Up (healthy)   9000/tcp\nmilvus-standalone   /tini -- milvus run standalone   Up             0.0.0.0:19530->19530/tcp, 0.0.0.0:9091->9091/tcp\n","$ CUDA_VISIBLE_DEVICES=0 ./milvus run standalone\n","$ CUDA_VISIBLE_DEVICES=0,1 ./milvus run standalone\n","# Stop Milvus\n$ sudo docker compose down\n\n# Delete service data\n$ sudo rm -rf volumes\n","docker cp :/milvus/configs/milvus.yaml milvus.yaml\n","vim milvus.yaml\n","...\ngpu:\n  initMemSize: 0\n  maxMemSize: 0\n...\n","docker cp milvus.yaml :/milvus/configs/milvus.yaml\n","docker stop \ndocker start \n"],"headingContent":"Run Milvus with GPU Support Using Docker Compose","anchorList":[{"label":"Run Milvus with GPU Support Using Docker Compose","href":"Run-Milvus-with-GPU-Support-Using-Docker-Compose","type":1,"isActive":false},{"label":"Prerequisites","href":"Prerequisites","type":2,"isActive":false},{"label":"Install Milvus","href":"Install-Milvus","type":2,"isActive":false},{"label":"Configure memory pool","href":"Configure-memory-pool","type":2,"isActive":false},{"label":"What's next","href":"Whats-next","type":2,"isActive":false}]}
    \ No newline at end of file
    diff --git a/localization/v2.4.x/site/en/getstarted/run-milvus-gpu/install_standalone-docker-compose-gpu.md b/localization/v2.4.x/site/en/getstarted/run-milvus-gpu/install_standalone-docker-compose-gpu.md
    index 0729277e6..2842f401c 100644
    --- a/localization/v2.4.x/site/en/getstarted/run-milvus-gpu/install_standalone-docker-compose-gpu.md
    +++ b/localization/v2.4.x/site/en/getstarted/run-milvus-gpu/install_standalone-docker-compose-gpu.md
    @@ -59,8 +59,8 @@ title: Run Milvus with GPU Support Using Docker Compose
             >
           
         

    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 and save it as docker-compose.yml manually, or with the following command.

    -
    $ wget https://github.com/milvus-io/milvus/releases/download/v2.4.18/milvus-standalone-docker-compose-gpu.yml -O docker-compose.yml
    +

    1. Download and configure the YAML file

    Download milvus-standalone-docker-compose-gpu.yml and save it as docker-compose.yml manually, or with the following command.

    +
    $ wget https://github.com/milvus-io/milvus/releases/download/v2.4.19/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/localization/v2.4.x/site/en/release_notes.json b/localization/v2.4.x/site/en/release_notes.json index 91f696d3a..f09b2d578 100644 --- a/localization/v2.4.x/site/en/release_notes.json +++ b/localization/v2.4.x/site/en/release_notes.json @@ -1 +1 @@ -{"codeList":[],"headingContent":"Release Notes","anchorList":[{"label":"Release Notes","href":"Release-Notes","type":1,"isActive":false},{"label":"v2.4.18","href":"v2418","type":2,"isActive":false},{"label":"v2.4.17","href":"v2417","type":2,"isActive":false},{"label":"v2.4.15","href":"v2415","type":2,"isActive":false},{"label":"v2.4.14","href":"v2414","type":2,"isActive":false},{"label":"v2.4.13-hotfix","href":"v2413-hotfix","type":2,"isActive":false},{"label":"[Deprecated] v2.4.13","href":"Deprecated-v2413","type":2,"isActive":false},{"label":"v2.4.12","href":"v2412","type":2,"isActive":false},{"label":"v2.4.11","href":"v2411","type":2,"isActive":false},{"label":"v2.4.10","href":"v2410","type":2,"isActive":false},{"label":"v2.4.9","href":"v249","type":2,"isActive":false},{"label":"v2.4.8","href":"v248","type":2,"isActive":false},{"label":"v2.4.6","href":"v246","type":2,"isActive":false},{"label":"v2.4.5","href":"v245","type":2,"isActive":false},{"label":"v2.4.4","href":"v244","type":2,"isActive":false},{"label":"v2.4.3","href":"v243","type":2,"isActive":false},{"label":"v2.4.1","href":"v241","type":2,"isActive":false},{"label":"v2.4.0","href":"v240","type":2,"isActive":false},{"label":"v2.4.0-rc.1","href":"v240-rc1","type":2,"isActive":false}]} \ No newline at end of file +{"codeList":[],"headingContent":"Release Notes","anchorList":[{"label":"Release Notes","href":"Release-Notes","type":1,"isActive":false},{"label":"v2.4.19","href":"v2419","type":2,"isActive":false},{"label":"v2.4.18","href":"v2418","type":2,"isActive":false},{"label":"v2.4.17","href":"v2417","type":2,"isActive":false},{"label":"v2.4.15","href":"v2415","type":2,"isActive":false},{"label":"v2.4.14","href":"v2414","type":2,"isActive":false},{"label":"v2.4.13-hotfix","href":"v2413-hotfix","type":2,"isActive":false},{"label":"[Deprecated] v2.4.13","href":"Deprecated-v2413","type":2,"isActive":false},{"label":"v2.4.12","href":"v2412","type":2,"isActive":false},{"label":"v2.4.11","href":"v2411","type":2,"isActive":false},{"label":"v2.4.10","href":"v2410","type":2,"isActive":false},{"label":"v2.4.9","href":"v249","type":2,"isActive":false},{"label":"v2.4.8","href":"v248","type":2,"isActive":false},{"label":"v2.4.6","href":"v246","type":2,"isActive":false},{"label":"v2.4.5","href":"v245","type":2,"isActive":false},{"label":"v2.4.4","href":"v244","type":2,"isActive":false},{"label":"v2.4.3","href":"v243","type":2,"isActive":false},{"label":"v2.4.1","href":"v241","type":2,"isActive":false},{"label":"v2.4.0","href":"v240","type":2,"isActive":false},{"label":"v2.4.0-rc.1","href":"v240-rc1","type":2,"isActive":false}]} \ No newline at end of file diff --git a/localization/v2.4.x/site/en/release_notes.md b/localization/v2.4.x/site/en/release_notes.md index b5928d7bc..91a36987a 100644 --- a/localization/v2.4.x/site/en/release_notes.md +++ b/localization/v2.4.x/site/en/release_notes.md @@ -19,6 +19,47 @@ 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.19

      Release Date: December 26, 2024

      + + + + + + + +
      Milvus versionPython SDK versionJava SDK versionNode.js SDK version
      2.4.192.4.132.4.92.4.9
      +

      Milvus 2.4.19 focuses on fixing issues in RBAC, Balancer, and loading processes, while also introducing several performance enhancements in areas such as PartitionKey Deletion and hybrid searching. We highly recommend upgrading to this version for increased stability and reliability.

      +

      Improvements

        +
      • Expression templates are introduced to accelerate hybrid searches. (#38624)
      • +
      • Additional metrics are provided for improved deletion monitoring. (#38746)
      • +
      • L0 file generation is restricted to specific partition for partitionKey deletion to reduce amplification. (#38232)
      • +
      +

      Bug fixes

        +
      • Fixed OOM issues by adding a memory factor to loading estimations. (#38721)
      • +
      • Fixed privilege group expansion when listing policies in RootCoord. (#38759)
      • +
      • Fixed access log retention, skipping empty log rotation. (#38661)
      • +
      • Fixed the balancer to avoid repeatedly overloading the same query node. (#38720)
      • +
      • Fixed issues with listing privilege groups and collections. (#38698)
      • +
      • Fixed load config updates not applying to loading collections. (#38596)
      • +
      • Fixed unexpected balance tasks triggered after QueryCoord restarts. (#38714)
      • +
      • Fixed zero read count during data import. (#38696)
      • +
      • Fixed Unicode decoding for JSON keys in expressions. (#38652)
      • +

      v2.4.18