docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update audit-jobs-via-api.md 

Grammar fixes and rewrites,
This commit is contained in:
Maria Bermudez 2018-10-01 11:28:55 -07:00 committed by GitHub
parent e5c77b38d6
commit b03d7233c9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
ee/dtr/admin/manage-jobs/audit-jobs-via-api.md
View File

@ -14,8 +14,8 @@ This covers troubleshooting batch jobs via the API and was introduced in DTR 2.2
### Job capacity ### Job capacity
Each job runner has a limited capacity and won't claim jobs that require an Each job runner has a limited capacity and will not claim jobs that require a
higher capacity. You can see the capacity of a job runner using the higher capacity. You can see the capacity of a job runner via the
`GET /api/v0/workers` endpoint: `GET /api/v0/workers` endpoint:
```json ```json
@ -35,8 +35,7 @@ higher capacity. You can see the capacity of a job runner using the
``` ```
This means that the worker with replica ID `000000000000` has a capacity of 1 This means that the worker with replica ID `000000000000` has a capacity of 1
`scan` and 1 `scanCheck`. If this worker notices that the following jobs `scan` and 1 `scanCheck`. Next, review the list of available jobs:
are available:
```json ```json
{ {
@ -69,8 +68,9 @@ are available:
} }
``` ```
Our worker will be able to pick up job id `0` and `2` since it has the capacity If worker `000000000000` notices the jobs
for both, while id `1` will have to wait until the previous scan job is complete: in `waiting` state above, then it will be able to pick up jobs `0` and `2` since it has the capacity
for both. Job `1` will have to wait until the previous scan job, `0`, is completed. The job queue will then look like:
```json ```json
{ {
@ -102,8 +102,8 @@ for both, while id `1` will have to wait until the previous scan job is complete
] ]
} }
``` ```
You can get the list of jobs, using the `GET /api/v0/jobs/` endpoint. Each job You can get a list of jobs via the `GET /api/v0/jobs/` endpoint. Each job
looks like this: looks like:
```json ```json
{ {
@ -126,7 +126,7 @@ looks like this:
"stopTimeout": "" "stopTimeout": ""
} }
``` ```
The fields of interest here are: The JSON fields of interest here are:
* `id`: The ID of the job * `id`: The ID of the job
* `workerID`: The ID of the worker in a DTR replica that is running this job * `workerID`: The ID of the worker in a DTR replica that is running this job
@ -170,7 +170,7 @@ see those jobs using the `GET /api/v0/crons` endpoint:
} }
``` ```
The `schedule` uses a Unix crontab syntax. The `schedule` field uses a Unix crontab syntax.
## Where to go next ## Where to go next