-
Notifications
You must be signed in to change notification settings - Fork 2k
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.
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
Stopped periodic batch job clutters job list #11256
Comments
Hi @EtienneBruines. The objects from a stopped job are not removed from Nomad state until the job_gc_threshold has been reached. Until that time, the objects, as you described are still visible. When stopping a job via the CLI or API, it is possible to specify a |
@jrasell They weren't visible to begin with, though. They only appeared as I removed the job |
Thanks for the clarification @EtienneBruines. This does seem like undesirable/unexpected behaviour and i'll mark this for our UI experts to investigate further. |
Hi and thank you for your patience on this issue! The jobs index page will no longer be cluttered by child jobs, as they're no longer fetched until a parent job is clicked-into in the UI. This work went out in v1.8 and details can be found at #20452 |
Nomad version
Nomad v1.1.5 (117a23d)
Operating system and Environment details
Server runs Ubuntu 20.04.3 LTS
Issue
After stopping a periodic batch job, the jobs listing is cluttered.
Reproduction steps
Stop
for that job (not for the allocation, but for the job itself)Possibly important: the job is in the non-default namespace.
Expected Result
Not to see a list of all allocations/invocations/evaluations (?) of that stopped job.
Actual Result
The cli
nomad job status
shows the same.Job file (if appropriate)
Nomad Server logs (if appropriate)
Nomad Client logs (if appropriate)
The text was updated successfully, but these errors were encountered: