From 770aa5ce2474617e7661babbc21d422822f4e20e Mon Sep 17 00:00:00 2001 From: Sergey Smolnikov Date: Mon, 8 Jul 2024 15:00:07 +0200 Subject: [PATCH] Removed `DeadlineExceeded` from job-scheduler batch job statuses. (#369) --- public-site/docs/guides/jobs/job-manager-and-job-api.md | 2 +- public-site/docs/radix-config/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/public-site/docs/guides/jobs/job-manager-and-job-api.md b/public-site/docs/guides/jobs/job-manager-and-job-api.md index 93afb5a9..f4fdf3ac 100644 --- a/public-site/docs/guides/jobs/job-manager-and-job-api.md +++ b/public-site/docs/guides/jobs/job-manager-and-job-api.md @@ -142,7 +142,7 @@ Once the job has been created successfully, the `job-scheduler` responds to `bac - `name` is the unique name for the job. This is the value to be used in the `GET /api/v1/jobs/{jobName}` and `DELETE /api/v1/jobs/{jobName}` methods. It is also the host name to connect to running job's container, with its exposed port, e.g. `http://batch-compute-20230220100755-xkoxce5g-mll3kxxh:3000` - `started` is the date and time the job was started. It is represented in RFC3339 form and is in UTC. - `ended` is the date and time the job successfully ended. Also represented in RFC3339 form and is in UTC. This value is only set for `Succeeded` jobs. -- `status` is the current status of the job. Possible values are `Waiting`, `Stopping`, `Stopped`, `Active`, `Running`, `Succeeded`, `Failed`, `DeadlineExceeded`. `Active` status means that the job has a replica created, but this replica is not ready (due to such reasons as volume mount is not ready, or it is a problem to schedule replica on a node because not enough memory available, etc.), this status can remain forever. Status `Failed` if the job's replica container exits with a non-zero exit code, and `Succeeded` if the exit code is zero. +- `status` is the current status of the job. Possible values are `Waiting`, `Stopping`, `Stopped`, `Active`, `Running`, `Succeeded`, `Failed`. `Active` status means that the job has a replica created, but this replica is not ready (due to such reasons as volume mount is not ready, or it is a problem to schedule replica on a node because not enough memory available, etc.), this status can remain forever. Status `Failed` if the job's replica container exits with a non-zero exit code, and `Succeeded` if the exit code is zero. ## Getting the status of all existing jobs diff --git a/public-site/docs/radix-config/index.md b/public-site/docs/radix-config/index.md index d21c1528..cf5b3f2b 100644 --- a/public-site/docs/radix-config/index.md +++ b/public-site/docs/radix-config/index.md @@ -1221,7 +1221,7 @@ spec: - `condition` - `Any`, `All` - `operator` - `In`, `NotIn` - `jobStatuses` - `Waiting`, `Active`, `Running`, `Succeeded`, `Failed`, `Stopped` -- `batchStatus` - `Waiting`, `Active`, `Running`, `Succeeded`, `Failed`, `Stopping`, `Stopped`, `DeadlineExceeded`, `Completed` +- `batchStatus` - `Waiting`, `Active`, `Running`, `Succeeded`, `Failed`, `Stopping`, `Stopped`, `Completed` Rules are applied in the order from top to bottom in the rules list. When any rule matches, rules following it are ignored.