Skip to content

Commit 82c6a28

Browse files
AnthonyTsu1984AnthonyTsu1984
authored
Merge pull request #3367 from milvus-io/AnthonyTsu1984-patch-1
Change 'indexNode' to 'dataNode' in GPU config
2 parents 387c89f + 84b93ee commit 82c6a28

File tree

1 file changed

+32
-29
lines changed

1 file changed

+32
-29
lines changed

‎site/en/getstarted/run-milvus-gpu/install_cluster-helm-gpu.md‎

Lines changed: 32 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Milvus with GPU support allows you to assign one or more GPU devices.
8282
8383
```bash
8484
cat <<EOF > custom-values.yaml
85-
indexNode:
85+
dataNode:
8686
resources:
8787
requests:
8888
nvidia.com/gpu: "1"
@@ -126,7 +126,7 @@ In addition to a single GPU device, you can also assign multiple GPU devices to
126126
127127
```bash
128128
cat <<EOF > custom-values.yaml
129-
indexNode:
129+
dataNode:
130130
resources:
131131
requests:
132132
nvidia.com/gpu: "2"
@@ -141,11 +141,11 @@ In addition to a single GPU device, you can also assign multiple GPU devices to
141141
EOF
142142
```
143143
144-
In the configuration above, the indexNode and queryNode share two GPUs. To assign different GPUs to the indexNode and the queryNode, you can modify the configuration accordingly by setting `extraEnv` in the configuration file as follows:
144+
In the configuration above, there are four CPUs available, and each dataNode and queryNode uses two GPUs. To assign different GPUs to the dataNode and the queryNode, you can modify the configuration accordingly by setting `extraEnv` in the configuration file as follows:
145145
146146
```bash
147147
cat <<EOF > custom-values.yaml
148-
indexNode:
148+
dataNode:
149149
resources:
150150
requests:
151151
nvidia.com/gpu: "1"
@@ -184,7 +184,7 @@ In addition to a single GPU device, you can also assign multiple GPU devices to
184184
185185
```bash
186186
cat <<EOF > custom-values.yaml
187-
indexNode:
187+
dataNode:
188188
resources:
189189
requests:
190190
nvidia.com/gpu: "2"
@@ -199,11 +199,11 @@ In addition to a single GPU device, you can also assign multiple GPU devices to
199199
EOF
200200
```
201201
202-
In the configuration above, the indexNode and queryNode share two GPUs. To assign different GPUs to the indexNode and the queryNode, you can modify the configuration accordingly by setting extraEnv in the configuration file as follows:
202+
In the configuration above, there are four CPUs available, and each dataNode and queryNode uses two GPUs. To assign different GPUs to the dataNode and the queryNode, you can modify the configuration accordingly by setting extraEnv in the configuration file as follows:
203203
204204
```bash
205205
cat <<EOF > custom-values.yaml
206-
indexNode:
206+
dataNode:
207207
resources:
208208
requests:
209209
nvidia.com/gpu: "1"
@@ -242,28 +242,31 @@ After Milvus starts, the `READY` column displays `1/1` for all pods.
242242
243243
```shell
244244
NAME READY STATUS RESTARTS AGE
245-
my-release-etcd-0 1/1 Running 0 3m23s
246-
my-release-etcd-1 1/1 Running 0 3m23s
247-
my-release-etcd-2 1/1 Running 0 3m23s
248-
my-release-milvus-datacoord-6fd4bd885c-gkzwx 1/1 Running 0 3m23s
249-
my-release-milvus-datanode-68cb87dcbd-4khpm 1/1 Running 0 3m23s
250-
my-release-milvus-indexcoord-5bfcf6bdd8-nmh5l 1/1 Running 0 3m23s
251-
my-release-milvus-indexnode-5c5f7b5bd9-l8hjg 1/1 Running 0 3m24s
252-
my-release-milvus-proxy-6bd7f5587-ds2xv 1/1 Running 0 3m24s
253-
my-release-milvus-querycoord-579cd79455-xht5n 1/1 Running 0 3m24s
254-
my-release-milvus-querynode-5cd8fff495-k6gtg 1/1 Running 0 3m24s
255-
my-release-milvus-rootcoord-7fb9488465-dmbbj 1/1 Running 0 3m23s
256-
my-release-minio-0 1/1 Running 0 3m23s
257-
my-release-minio-1 1/1 Running 0 3m23s
258-
my-release-minio-2 1/1 Running 0 3m23s
259-
my-release-minio-3 1/1 Running 0 3m23s
260-
my-release-pulsar-autorecovery-86f5dbdf77-lchpc 1/1 Running 0 3m24s
261-
my-release-pulsar-bookkeeper-0 1/1 Running 0 3m23s
262-
my-release-pulsar-bookkeeper-1 1/1 Running 0 98s
263-
my-release-pulsar-broker-556ff89d4c-2m29m 1/1 Running 0 3m23s
264-
my-release-pulsar-proxy-6fbd75db75-nhg4v 1/1 Running 0 3m23s
265-
my-release-pulsar-zookeeper-0 1/1 Running 0 3m23s
266-
my-release-pulsar-zookeeper-metadata-98zbr 0/1 Completed 0 3m24s
245+
my-release-etcd-0 1/1 Running 0 3m24s
246+
my-release-etcd-1 1/1 Running 0 3m24s
247+
my-release-etcd-2 1/1 Running 0 3m24s
248+
my-release-milvus-datanode-698dbf7d77-rjkkq 1/1 Running 0 3m24s
249+
my-release-milvus-mixcoord-856d666559-rpj8z 1/1 Running 0 3m24s
250+
my-release-milvus-proxy-7f7cf47689-pzltw 1/1 Running 0 3m24s
251+
my-release-milvus-querynode-7fb6d5b5f8-92phj 1/1 Running 0 3m24s
252+
my-release-milvus-streamingnode-5867bfbcbf-cg9xx 1/1 Running 0 3m24s
253+
my-release-minio-0 1/1 Running 0 3m24s
254+
my-release-minio-1 1/1 Running 0 3m24s
255+
my-release-minio-2 1/1 Running 0 3m24s
256+
my-release-minio-3 1/1 Running 0 3m24s
257+
my-release-pulsarv3-bookie-0 1/1 Running 0 3m24s
258+
my-release-pulsarv3-bookie-1 1/1 Running 0 3m24s
259+
my-release-pulsarv3-bookie-2 1/1 Running 0 3m24s
260+
my-release-pulsarv3-bookie-init-p8hcq 0/1 Completed 0 3m24s
261+
my-release-pulsarv3-broker-0 1/1 Running 0 3m24s
262+
my-release-pulsarv3-broker-1 1/1 Running 0 3m24s
263+
my-release-pulsarv3-proxy-0 1/1 Running 0 3m24s
264+
my-release-pulsarv3-proxy-1 1/1 Running 0 3m24s
265+
my-release-pulsarv3-pulsar-init-8kjsj 0/1 Completed 0 3m24s
266+
my-release-pulsarv3-recovery-0 1/1 Running 0 3m24s
267+
my-release-pulsarv3-zookeeper-0 1/1 Running 0 3m24s
268+
my-release-pulsarv3-zookeeper-1 1/1 Running 0 3m24s
269+
my-release-pulsarv3-zookeeper-2 1/1 Running 0 3m24s
267270
```
268271
269272
- Milvus standalone

0 commit comments

Comments
 (0)