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

Ignore the previous job_id inside fill_reservations() #138

Closed
yahoNanJing opened this issue Aug 15, 2022 · 0 comments · Fixed by #141
Closed

Ignore the previous job_id inside fill_reservations() #138

yahoNanJing opened this issue Aug 15, 2022 · 0 comments · Fixed by #141
Labels
enhancement New feature or request

Comments

@yahoNanJing
Copy link
Contributor

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

Current strategy of filling reservation will leverage the previous job_id in the ExecutorReservation to give higher priority for that job scheduling. However, it will cause starvation issue when there are jobs with huge number of tasks.

Describe the solution you'd like

It's better for the fill_reservations() to choose tasks fairly for each job and let the scheduler decides which job to be scheduled first which may be implemented by a few queues maintained by the scheduler in the future.

Describe alternatives you've considered

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant