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.

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

Closed
EtienneBruines opened this issue Oct 4, 2021 · 4 comments
Closed

Stopped periodic batch job clutters job list #11256

EtienneBruines opened this issue Oct 4, 2021 · 4 comments
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/batch Issues related to batch jobs and scheduling theme/ui type/bug

Comments

@EtienneBruines
Copy link
Contributor

EtienneBruines commented Oct 4, 2021

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

  1. Create a batch job that runs periodically, let's say every 1 minute
  2. Let that job run a few times (e.g. wait 5 minutes)
  3. Go into the UI and press Stop for that job (not for the allocation, but for the job itself)
  4. Wait a few minutes (?)
  5. Go into the list of jobs and verify that the job is stopped / dead.

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

Screenshot_20211004_105954

The cli nomad job status shows the same.

Job file (if appropriate)

Nomad Server logs (if appropriate)

Nomad Client logs (if appropriate)

@jrasell
Copy link
Member

jrasell commented Oct 6, 2021

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 purge parameter which stops the job and immediately garbage collects its information. I wonder if we should therefore make this setting available via the UI?

@EtienneBruines
Copy link
Contributor Author

@jrasell They weren't visible to begin with, though. They only appeared as I removed the job mossaino-certificate-udpatear itself. I can imagine that previously, they were "grouped" under that job, and when I stopped that job, they all appeared individually?

@jrasell
Copy link
Member

jrasell commented Oct 6, 2021

Thanks for the clarification @EtienneBruines. This does seem like undesirable/unexpected behaviour and i'll mark this for our UI experts to investigate further.

@jrasell jrasell added stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/batch Issues related to batch jobs and scheduling theme/ui labels Oct 6, 2021
@philrenaud philrenaud moved this to Icebox in Nomad UI Jun 10, 2022
@ChaiWithJai ChaiWithJai moved this from Backlog to Todo in Nomad UI Dec 14, 2022
@ChaiWithJai ChaiWithJai self-assigned this Dec 14, 2022
@philrenaud
Copy link
Contributor

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

@github-project-automation github-project-automation bot moved this from Todo to Done in Nomad UI Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/batch Issues related to batch jobs and scheduling theme/ui type/bug
Projects
Status: Done
Development

No branches or pull requests

4 participants