Return-Path: 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 D0D6418B23 for ; Mon, 18 Jan 2016 09:12:40 +0000 (UTC) Received: (qmail 1765 invoked by uid 500); 18 Jan 2016 09:12:40 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 1695 invoked by uid 500); 18 Jan 2016 09:12:40 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 1385 invoked by uid 99); 18 Jan 2016 09:12:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jan 2016 09:12:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 280332C1F72 for ; Mon, 18 Jan 2016 09:12:40 +0000 (UTC) Date: Mon, 18 Jan 2016 09:12:40 +0000 (UTC) From: "Arun Suresh (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-2885) Create AMRMProxy request interceptor for distributed scheduling decisions for queueable containers 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-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2885: ------------------------------ Attachment: YARN-2885-yarn-2877.v6.patch Thanks for the comments [~kishorch] and [~giovanni.fumarola]. I have updated the patch based on your suggestions: # Updated the {{RequestInterceptor}} to implement the {{DistributedSchedulingProtocol}} instead of the {{ApplicationMasterProtocol}} : This essentially does not require any much change in the implementing interceptors since 1) the former extends the latter and 2) the two extra methods have a default implementation in the {{AbstractRequestInterceptor}}, so if it not concerned with Distributed Scheduling, it will not have to deal with it. # Updated the {{DefaultRequestInterceptor}} to talk to the RM using the {{DistributedSchedulingProtocol}} instead of the {{ApplicationMasterProtocol}}. # Removed {{LocalScheduler}} from the end of the chain.. and put back the DefaultRequestInterceptor Do let me know what you think.. > Create AMRMProxy request interceptor for distributed scheduling decisions for queueable containers > -------------------------------------------------------------------------------------------------- > > Key: YARN-2885 > URL: https://issues.apache.org/jira/browse/YARN-2885 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager, resourcemanager > Reporter: Konstantinos Karanasos > Assignee: Arun Suresh > Attachments: YARN-2885-yarn-2877.001.patch, YARN-2885-yarn-2877.002.patch, YARN-2885-yarn-2877.full-2.patch, YARN-2885-yarn-2877.full-3.patch, YARN-2885-yarn-2877.full.patch, YARN-2885-yarn-2877.v4.patch, YARN-2885-yarn-2877.v5.patch, YARN-2885-yarn-2877.v6.patch, YARN-2885_api_changes.patch > > > We propose to add a Local ResourceManager (LocalRM) to the NM in order to support distributed scheduling decisions. > Architecturally we leverage the RMProxy, introduced in YARN-2884. > The LocalRM makes distributed decisions for queuable containers requests. > Guaranteed-start requests are still handled by the central RM. -- This message was sent by Atlassian JIRA (v6.3.4#6332)