Hi together,
I was scrolling through Preemptor.java and noticed that tasks might be
preempted unnecessarily.
If I am not mistaken, the code works as follows:
for slave in slaves:
while SchedulingFilter.filter is still yielding vetos:
add preemptable task of slave to list toPre
Thanks for raising the concern!
> Unfortunately, it seems the preemptor cannot handle constraints
Sounds like you are saying the Preemptor is only matching resources and not
constraints?
I'm on a phone, so I may have missed something, but my read is that the
preemptor lets SchedulingFilter.filte
Hi Bill,
you are right that the SchedulingFilter deals with constraints. However,
the preemptor seems to be reacting poorly when a job cannot be scheduled
due to such a constaint. Let me explain.
The preemptor cannot distinguish whether he sees a veto because of a
mismatched constraint or due to
>
> assumes the latter
I think i see what you're saying, but i believe this is a case of
performing unnecessary work rather than unnecessarily evicting tasks.
Consider the case you describe, where there are tasks on a host and a
pending task that can preempt them, but due to constraints may not
