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

Update Slurm shredder to ignore non-ended job states #1362

Merged
merged 2 commits into from Jul 2, 2020

Conversation

jtpalmer
Copy link
Contributor

@jtpalmer jtpalmer commented Jul 1, 2020

Description

Instead of shredding only jobs that are expected to have ended the shredder will now be able to shred all jobs and ignore those that are known to not have not ended. Also changes the Slurm helper script to query for jobs in all states.

Motivation and Context

Slurm added a new job state and I didn't notice.

See #1107

and https://app.asana.com/0/342819846538629/1144930465270465/f

Tests performed

Added more shredder tests.

Needs manual testing.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project as found in the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@jtpalmer jtpalmer added enhancement Enhancement of the functionality of an existing feature Category:ETL Extract Transform Load labels Jul 1, 2020
@jtpalmer jtpalmer added this to the 9.0.0 milestone Jul 1, 2020
@jtpalmer jtpalmer changed the title Update Slurm shredder to ignore non-ended jobs Update Slurm shredder to ignore non-ended job states Jul 1, 2020
Also changes the Slurm helper script to query for jobs in all states.
@jpwhite4
Copy link
Member

jpwhite4 commented Jul 2, 2020

Looks good. Perhaps add a sentence or two in the upgrade notes to explain that the --state filter is no longer needed in the sacct command line when running sacct manually.

Also is it worth adding an entry to the FAQ to explain what to do when they see a warning message like 'Found job with unknown state'. Presumably they are expected to go into a blind panic and delete random tables from the database until the error goes away.

@jtpalmer
Copy link
Contributor Author

jtpalmer commented Jul 2, 2020

@jpwhite4 Thank you for reminding me about that. I was planning to do something like that, but forgot.

@jtpalmer jtpalmer merged commit b6c11d2 into ubccr:xdmod9.0 Jul 2, 2020
@jtpalmer jtpalmer deleted the slurm-job-states branch July 2, 2020 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category:ETL Extract Transform Load enhancement Enhancement of the functionality of an existing feature
Projects
None yet
3 participants