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

Limit the started jobs per "dataset namespace" #626

Merged
merged 3 commits into from
Oct 27, 2022

Conversation

severo
Copy link
Collaborator

@severo severo commented Oct 27, 2022

The env var MAX_JOBS_PER_DATASET is rename MAX_JOBS_PER_NAMESPACE.

Also: select the next job among the namespaces with the least number of started jobs in order to avoid having all the workers dedicated to the same user if others are waiting. The namespace is the user, the org, or the dataset name for canonical datasets.

Deployment: the collection is now called jobs_blue (see blue/green deployment). Once deployed, look at the old "jobs" collection, relaunch the jobs for the waiting or started datasets, then delete the "jobs" collection.

and also: select the next dataset among the namespaces with the least
number of started jobs, in order to avoid having all the workers
dedicated to the same user, if others are waiting. The namespace is the
user or the org, or the dataset name itself for canonical datasets.

Deployment: the collection is now called jobs_blue (see blue/gree
deployment). Once deployed, look at the old "jobs" collection, relaunch
the jobs for the waiting or started datasets, then delete the "jobs"
collection.
and update doc and helm values
@severo severo changed the title feat: 🎸 limit the started datasets per namespace Limit the started jobs per "dataset namespace" Oct 27, 2022
@severo severo marked this pull request as ready for review October 27, 2022 12:20
@HuggingFaceDocBuilder
Copy link
Collaborator

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

@severo severo merged commit f35071f into main Oct 27, 2022
@severo severo deleted the depriorize-users-with-started-jobs branch October 27, 2022 12:28
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.

2 participants