Return-Path: 
 <yarn-issues-return-19205-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id C962F101E7
	for <apmail-hadoop-yarn-issues-archive@minotaur.apache.org>;
 Wed,  4 Dec 2013 04:24:46 +0000 (UTC)
Received: (qmail 59066 invoked by uid 500); 4 Dec 2013 04:24:44 -0000
Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org
Received: (qmail 58733 invoked by uid 500); 4 Dec 2013 04:24:38 -0000
Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:yarn-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:yarn-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:yarn-issues@hadoop.apache.org>
List-Id: <yarn-issues.hadoop.apache.org>
Reply-To: yarn-issues@hadoop.apache.org
Delivered-To: mailing list yarn-issues@hadoop.apache.org
Received: (qmail 58716 invoked by uid 99); 4 Dec 2013 04:24:35 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Dec 2013 04:24:35 +0000
Date: Wed, 4 Dec 2013 04:24:35 +0000 (UTC)
From: "Alejandro Abdelnur (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12682593.1386121977046.68097.1386131075910@arcas>
In-Reply-To: <JIRA.12682593.1386121977046@arcas>
References: <JIRA.12682593.1386121977046@arcas>
Subject: [jira] [Commented] (YARN-1471) The SLS simulator is not running the
 preemption policy for CapacityScheduler
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/YARN-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838579#comment-13838579 ] 

Alejandro Abdelnur commented on YARN-1471:
------------------------------------------

[~curino], I'm not familiar on how the ProportionalCapacityPreemptionPolicy gets hold of data from the CapacityScheduler. The SLS simply wraps the Scheduler implementation using a proxy pattern. Thus, the scheduler API is fully exposed even if wrapped. If the ProportionalCapacityPreemptionPolicy cast the Scheduler interface to the CapacityScheduler class, I would be inclined to say that this is not a SLS issue but a ProportionalCapacityPreemptionPolicy issue. Are the methods of the CapacityScheduler used by the ProportionalCapacityPreemptionPolicy general purpose to qualify being in the Scheduler API? If not, how about implementing a 'safety valve', something like {{public T <T> getComponent(Class<T> klass)}} in the Scheduler API, and the contract is to return NULL if such component is not implemented by the scheduler. Would something like this work?

> The SLS simulator is not running the preemption policy for CapacityScheduler
> ----------------------------------------------------------------------------
>
>                 Key: YARN-1471
>                 URL: https://issues.apache.org/jira/browse/YARN-1471
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Carlo Curino
>            Assignee: Wei Yan
>            Priority: Minor
>
> The simulator does not run the ProportionalCapacityPreemptionPolicy monitor.  This is because the policy needs to interact with a CapacityScheduler, and the wrapping done by the simulator breaks this. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)