You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Download the installation file for Milvus [standalone](https://github.com/milvus-io/milvus/releases/download/v2.5.0/milvus-standalone-docker-compose.yml), and save it as `docker-compose.yml`.
181
+
Download the installation file for Milvus [standalone](https://github.com/milvus-io/milvus/releases/download/v2.5.1/milvus-standalone-docker-compose.yml), and save it as `docker-compose.yml`.
Copy file name to clipboardexpand all lines: v2.5.x/site/en/adminGuide/operator.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Milvus cluster depends on components including object storage, etcd, and Pulsar.
12
12
13
13
This topic assumes that you have deployed Milvus Operator.
14
14
15
-
<divclass="alert note">See <ahref="https://milvus.io/docs/v2.5.0/install_cluster-milvusoperator.md">Deploy Milvus Operator</a> for more information. </div>
15
+
<divclass="alert note">See <ahref="https://milvus.io/docs/v2.5.1/install_cluster-milvusoperator.md">Deploy Milvus Operator</a> for more information. </div>
16
16
17
17
You need to specify a configuration file for using Milvus Operator to start a Milvus cluster.
This topic describes how to upgrade your Milvus using Docker Compose.
12
12
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.5.0.
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.5.1.
14
14
15
15
## Upgrade Milvus by changing its image
16
16
@@ -24,35 +24,35 @@ In normal cases, you can upgrade Milvus as follows:
24
24
...
25
25
rootcoord:
26
26
container_name: milvus-rootcoord
27
-
image: milvusdb/milvus:v2.5.0
27
+
image: milvusdb/milvus:v2.5.1
28
28
...
29
29
proxy:
30
30
container_name: milvus-proxy
31
-
image: milvusdb/milvus:v2.5.0
31
+
image: milvusdb/milvus:v2.5.1
32
32
...
33
33
querycoord:
34
34
container_name: milvus-querycoord
35
-
image: milvusdb/milvus:v2.5.0
35
+
image: milvusdb/milvus:v2.5.1
36
36
...
37
37
querynode:
38
38
container_name: milvus-querynode
39
-
image: milvusdb/milvus:v2.5.0
39
+
image: milvusdb/milvus:v2.5.1
40
40
...
41
41
indexcoord:
42
42
container_name: milvus-indexcoord
43
-
image: milvusdb/milvus:v2.5.0
43
+
image: milvusdb/milvus:v2.5.1
44
44
...
45
45
indexnode:
46
46
container_name: milvus-indexnode
47
-
image: milvusdb/milvus:v2.5.0
47
+
image: milvusdb/milvus:v2.5.1
48
48
...
49
49
datacoord:
50
50
container_name: milvus-datacoord
51
-
image: milvusdb/milvus:v2.5.0
51
+
image: milvusdb/milvus:v2.5.1
52
52
...
53
53
datanode:
54
54
container_name: milvus-datanode
55
-
image: milvusdb/milvus:v2.5.0
55
+
image: milvusdb/milvus:v2.5.1
56
56
```
57
57
58
58
2. Run the following commands to perform the upgrade.
@@ -80,7 +80,7 @@ In normal cases, you can upgrade Milvus as follows:
80
80
runWithBackup: true
81
81
config:
82
82
sourceVersion: 2.1.4 # Specify your milvus version
Copy file name to clipboardexpand all lines: v2.5.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -85,11 +85,11 @@ zilliztech/milvus 4.1.0 2.3.0 Milvus is an ope
85
85
86
86
You can choose the upgrade path for your Milvus as follows:
87
87
88
-
<divstyle="display: none;">- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.5.0.</div>
88
+
<divstyle="display: none;">- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.5.1.</div>
89
89
90
-
-[Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.5.0.
90
+
-[Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.5.1.
91
91
92
-
-[Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.5.0.
92
+
-[Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.5.1.
93
93
94
94
<divstyle="display: none;">
95
95
@@ -111,10 +111,10 @@ The script applies only to the upgrade of Milvus installed with Helm. The follow
111
111
|`w`| New Milvus image tag |`milvusdb/milvus:v2.2.3`| True |
112
112
|`o`| Operation |`update`| False |
113
113
114
-
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.5.0.
114
+
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.5.1.
Once you have upgraded your Milvus operator to the latest version, you have the following choices:
28
28
29
-
- To upgrade Milvus from v2.2.3 or later releases to 2.5.0, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade).
30
-
- To upgrade Milvus from a minor release before v2.2.3 to 2.5.0, you are advised to [upgrade Milvus by changing its image version](#Upgrade-Milvus-by-changing-its-image).
31
-
- To upgrade Milvus from v2.1.x to 2.5.0, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade.
29
+
- To upgrade Milvus from v2.2.3 or later releases to 2.5.1, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade).
30
+
- To upgrade Milvus from a minor release before v2.2.3 to 2.5.1, you are advised to [upgrade Milvus by changing its image version](#Upgrade-Milvus-by-changing-its-image).
31
+
- To upgrade Milvus from v2.1.x to 2.5.1, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade.
32
32
33
33
## Conduct a rolling upgrade
34
34
@@ -47,7 +47,7 @@ spec:
47
47
components:
48
48
enableRollingUpdate: true
49
49
imageUpdateMode: rollingUpgrade # Default value, can be omitted
50
-
image: milvusdb/milvus:v2.5.0
50
+
image: milvusdb/milvus:v2.5.1
51
51
```
52
52
53
53
In this above configuration file, set `spec.components.enableRollingUpdate` to `true` and set `spec.components.image` to the desired Milvus version.
@@ -63,7 +63,7 @@ spec:
63
63
components:
64
64
enableRollingUpdate: true
65
65
imageUpdateMode: all
66
-
image: milvusdb/milvus:v2.5.0
66
+
image: milvusdb/milvus:v2.5.1
67
67
```
68
68
69
69
You can set `spec.components.imageUpdateMode` to `rollingDowngrade` to have Milvus replace coordinator pod images with a lower version.
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.5.0.
115
+
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.5.1.
116
116
117
117
### 1. Create a `.yaml` file for metadata migration
118
118
119
-
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.5.0`. This means that your Milvus cluster will be upgraded from v2.1.4 to v2.5.0.
119
+
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.5.1`. This means that your Milvus cluster will be upgraded from v2.1.4 to v2.5.1.
This topic describes how to upgrade your Milvus using Docker Compose.
16
16
17
-
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.5.0.
17
+
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.5.1.
18
18
19
19
<divclass="alter note">
20
20
@@ -32,7 +32,7 @@ In normal cases, you can upgrade Milvus as follows:
32
32
...
33
33
standalone:
34
34
container_name: milvus-standalone
35
-
image: milvusdb/milvus:v2.5.0
35
+
image: milvusdb/milvus:v2.5.1
36
36
```
37
37
38
38
2. Run the following commands to perform the upgrade.
@@ -60,7 +60,7 @@ In normal cases, you can upgrade Milvus as follows:
60
60
runWithBackup: true
61
61
config:
62
62
sourceVersion: 2.1.4 # Specify your milvus version
Copy file name to clipboardexpand all lines: v2.5.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md
+14-14
Original file line number
Diff line number
Diff line change
@@ -86,11 +86,11 @@ zilliztech/milvus 4.1.0 2.3.0 Milvus is an ope
86
86
87
87
You can choose the upgrade path for your Milvus as follows:
88
88
89
-
<divstyle="display: none;">- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.5.0.</div>
89
+
<divstyle="display: none;">- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.5.1.</div>
90
90
91
-
-[Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.5.0.
91
+
-[Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.5.1.
92
92
93
-
-[Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.5.0.
93
+
-[Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.5.1.
94
94
95
95
<divstyle="display:none;">
96
96
@@ -112,10 +112,10 @@ The script applies only to the upgrade of Milvus installed with Helm. The follow
112
112
|`w`| New Milvus image tag |`milvusdb/milvus:v2.2.3`| True |
113
113
|`o`| Operation |`update`| False |
114
114
115
-
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.5.0.
115
+
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.5.1.
Once you have upgraded your Milvus operator to the latest version, you have the following choices:
28
28
29
-
- To upgrade Milvus from v2.2.3 or later releases to 2.5.0, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade).
30
-
- To upgrade Milvus from a minor release before v2.2.3 to 2.5.0, you are advised to [upgrade Milvus by changing its image version](#Upgrade-Milvus-by-changing-its-image).
31
-
- To upgrade Milvus from v2.1.x to 2.5.0, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade.
29
+
- To upgrade Milvus from v2.2.3 or later releases to 2.5.1, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade).
30
+
- To upgrade Milvus from a minor release before v2.2.3 to 2.5.1, you are advised to [upgrade Milvus by changing its image version](#Upgrade-Milvus-by-changing-its-image).
31
+
- To upgrade Milvus from v2.1.x to 2.5.1, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade.
32
32
33
33
## Conduct a rolling upgrade
34
34
@@ -47,7 +47,7 @@ spec:
47
47
components:
48
48
enableRollingUpdate: true
49
49
imageUpdateMode: rollingUpgrade # Default value, can be omitted
50
-
image: milvusdb/milvus:v2.5.0
50
+
image: milvusdb/milvus:v2.5.1
51
51
```
52
52
53
53
In this above configuration file, set `spec.components.enableRollingUpdate` to `true` and set `spec.components.image` to the desired Milvus version.
@@ -63,7 +63,7 @@ spec:
63
63
components:
64
64
enableRollingUpdate: true
65
65
imageUpdateMode: all
66
-
image: milvusdb/milvus:v2.5.0
66
+
image: milvusdb/milvus:v2.5.1
67
67
```
68
68
69
69
You can set `spec.components.imageUpdateMode` to `rollingDowngrade` to have Milvus replace coordinator pod images with a lower version.
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.5.0.
116
+
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.5.1.
117
117
118
118
### 1. Create a `.yaml` file for metadata migration
119
119
120
-
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.5.0`. This means that your Milvus instance will be upgraded from v2.1.4 to v2.5.0.
120
+
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.5.1`. This means that your Milvus instance will be upgraded from v2.1.4 to v2.5.1.
0 commit comments