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

Scheduling controls on queues and labels #3751

Closed
wants to merge 8 commits into from

Conversation

MustafaI
Copy link
Contributor

@MustafaI MustafaI commented Jun 24, 2024

Summary of changes:

  • Ability to pause/resume scheduling per-queue
    • Queued demand for paused queues not considered in fair share calculations
  • Ability to label queues
  • Armadactl scheduling controls based on the above features:
    • Added control-scheduling command with pause and resume sub-commands
    • match-labels, match-queues, dry-run and inverse flags on sub-commands allow better transparency and control on actions being taken.

Also renamed testfixture constants to be more consistent with others
We had a bug where unfeasibleSchedulingKeys was being populated incorrectly, which led to all jobs of a particular shape being banned for that scheduling round. By fixing this bug we also broke some tests which relied on UnsuccessfulJobSchedulingContexts being populated correctly. However, this data structure was only populated if a job was marked as unsuccessful because it's scheduling key was in unfeasibleSchedulingKeys. Fixing this bug should also fix inaccuracies in metrics, as well as provide better job scheduling reporting.
@MustafaI MustafaI closed this Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants