Project

General

Profile

Actions

action #40811

closed

Single Machine jobs starve clusters

Added by coolo over 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2018-09-10
Due date:
% Done:

0%

Estimated time:

Description

As the scheduler tries to fill all available slots, the workers that can run
multi machine and single machine jobs will be filled with single machine jobs
as the clusters don't fit. The only way that clusters fit is if 4 jobs finish
within one scheduling round.

This is a tricky problem in general, but it has been solved before :)

Actions #1

Updated by coolo over 6 years ago

The general idea is: whenver a job would be scheduled according to priority - but can't be scheduled due to cluster dependency, we increase a counter (or decrease the priority).
Once that counter reached a limit (or the priority turned 0), we reserve a worker slot for the job - and just won't allocate it until we have the full cluster.

Actions #2

Updated by coolo over 6 years ago

  • Target version changed from Ready to Current Sprint
Actions #3

Updated by coolo about 6 years ago

  • Status changed from New to Resolved
Actions #4

Updated by szarate about 6 years ago

  • Target version changed from Current Sprint to Done
Actions #5

Updated by coolo about 6 years ago

  • Target version changed from Done to Current Sprint
Actions #6

Updated by coolo about 6 years ago

  • Target version changed from Current Sprint to Done
Actions

Also available in: Atom PDF