Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove-status #369

Merged
merged 1 commit into from
Jul 8, 2024
Merged

remove-status #369

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion public-site/docs/guides/jobs/job-manager-and-job-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
2 changes: 1 addition & 1 deletion public-site/docs/radix-config/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down