Parallel Jobs with a *work queue*:

do not specify `.spec.completions`, default to `.spec.Parallelism`, not  default to 1
reviewable/pr2602/r1
ztewyk 2017-02-16 16:44:45 +08:00 committed by mengyuan
parent dc053ed54f
commit dfb8b79b15
1 changed files with 1 additions and 1 deletions

View File

@ -120,7 +120,7 @@ There are three main types of jobs:
- the job is complete when there is one successful pod for each value in the range 1 to `.spec.completions`.
- **not implemented yet:** each pod passed a different index in the range 1 to `.spec.completions`.
1. Parallel Jobs with a *work queue*:
- do not specify `.spec.completions`
- do not specify `.spec.completions`, default to `.spec.Parallelism`
- the pods must coordinate with themselves or an external service to determine what each should work on
- each pod is independently capable of determining whether or not all its peers are done, thus the entire Job is done.
- when _any_ pod terminates with success, no new pods are created.