Skip to content

Commit a84f5ab

Browse files
authored
Merge pull request #39139 from Zhuzhenghao/indexed-parallel-processing-static
[zh] Sync indexed-parallel-processing-static.md
2 parents 5af083b + 3416ada commit a84f5ab

File tree

1 file changed

+21
-10
lines changed

1 file changed

+21
-10
lines changed

content/zh-cn/docs/tasks/job/indexed-parallel-processing-static.md

Lines changed: 21 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -130,8 +130,8 @@ the start of the clip.
130130
索引完成意味着 Job 中的每个 Pod 都知道通过从剪辑开始计算帧数,来确定渲染和发布哪一帧。
131131

132132
<!--
133-
## Define an Indexed Job
134-
133+
## Define an Indexed Job
134+
135135
Here is a sample Job manifest that uses `Indexed` completion mode:
136136
-->
137137
## 定义索引作业 {#define-an-indexed-job}
@@ -172,9 +172,9 @@ like shown in the following example:
172172
{{< codenew language="yaml" file="application/job/indexed-job-vol.yaml" >}}
173173

174174
<!--
175-
## Running the Job
175+
## Running the Job
176176
177-
Now run the Job:
177+
Now run the Job:
178178
-->
179179
## 执行 Job {running-the-job}
180180

@@ -189,8 +189,6 @@ kubectl apply -f https://kubernetes.io/examples/application/job/indexed-job.yaml
189189
When you create this Job, the control plane creates a series of Pods, one for each index you specified. The value of `.spec.parallelism` determines how many can run at once whereas `.spec.completions` determines how many Pods the Job creates in total.
190190
191191
Because `.spec.parallelism` is less than `.spec.completions`, the control plane waits for some of the first Pods to complete before starting more of them.
192-
193-
Once you have created the Job, wait a moment then check on progress:
194192
-->
195193
当你创建此 Job 时,控制平面会创建一系列 Pod,你指定的每个索引都会运行一个 Pod。
196194
`.spec.parallelism` 的值决定了一次可以运行多少个 Pod,
@@ -199,14 +197,27 @@ Once you have created the Job, wait a moment then check on progress:
199197
因为 `.spec.parallelism` 小于 `.spec.completions`
200198
所以控制平面在启动更多 Pod 之前,将等待第一批的某些 Pod 完成。
201199

202-
创建 Job 后,稍等片刻,就能检查进度:
200+
<!--
201+
You can wait for the Job to succeed, with a timeout:
202+
-->
203+
你可以等待 Job 成功,等待时间可以设置超时限制:
204+
205+
```shell
206+
# 状况名称的检查不区分大小写
207+
kubectl wait --for=condition=complete --timeout=300s job/indexed-job
208+
```
209+
210+
<!--
211+
Now, describe the Job and check that it was successful.
212+
-->
213+
现在,描述 Job 并检查它是否成功。
203214

204215
```shell
205216
kubectl describe jobs/indexed-job
206217
```
207218

208219
<!--
209-
The output is similar to:
220+
The output is similar to:
210221
-->
211222
输出类似于:
212223

@@ -277,10 +288,10 @@ kubectl logs indexed-job-fdhq5 # 更改它以匹配来自该 Job 的 Pod 的名
277288
```
278289

279290
<!--
280-
The output is similar to:
291+
The output is similar to:
281292
-->
282293
输出类似于:
283294

284295
```
285296
xuq
286-
```
297+
```

0 commit comments

Comments
 (0)