Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 2119A200BE4 for ; Wed, 21 Dec 2016 19:07:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1F3A6160B39; Wed, 21 Dec 2016 18:07:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8B6C9160B18 for ; Wed, 21 Dec 2016 19:07:04 +0100 (CET) Received: (qmail 17550 invoked by uid 500); 21 Dec 2016 18:06:58 -0000 Mailing-List: contact issues-help@aurora.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.apache.org Delivered-To: mailing list issues@aurora.apache.org Received: (qmail 17537 invoked by uid 99); 21 Dec 2016 18:06:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Dec 2016 18:06:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 75BE02C2A68 for ; Wed, 21 Dec 2016 18:06:58 +0000 (UTC) Date: Wed, 21 Dec 2016 18:06:58 +0000 (UTC) From: "Mehrdad Nurolahzade (JIRA)" To: issues@aurora.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AURORA-1868) Evaluate multiple preemption proposals per round MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 21 Dec 2016 18:07:05 -0000 Mehrdad Nurolahzade created AURORA-1868: ------------------------------------------- Summary: Evaluate multiple preemption proposals per round Key: AURORA-1868 URL: https://issues.apache.org/jira/browse/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 (v6.3.4#6332)