aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mehrdad Nurolahzade (JIRA)" <>
Subject [jira] [Created] (AURORA-1868) Evaluate multiple preemption proposals per round
Date Wed, 21 Dec 2016 18:06:58 GMT
Mehrdad Nurolahzade created AURORA-1868:

             Summary: Evaluate multiple preemption proposals per round
                 Key: AURORA-1868
             Project: Aurora
          Issue Type: Story
          Components: Scheduler
            Reporter: Mehrdad Nurolahzade
            Priority: Minor

{{TaskScheduler}} makes an attempt to preempt already identified candidates through {{Preemptor}}
when it fails to schedule a task. However, {{Preemptor}} currently evaluates only one candidate
per invocation. A candidate may get vetoed at this point by scheduling filters. If a candidate
fails validation the task group might get penalized by {{TaskGroups}} to give {{PendingTaskProcessor}}
some time to find new preemption candidates; despite the fact that such a candidate may already
exist in slotCache. This penalty can result in expiration of {{slotCache}} entries, hence
slowing down the overall preemption process.

Consider modifying {{Preemptor}} so that it evaluates all existing preemption candidates before
giving up. This improvement comes at the price of reduced scheduling throughput. However,
in a near capacity cluster, reduced scheduling throughput is far more acceptable than failure
to schedule critical production services.

This message was sent by Atlassian JIRA

View raw message