Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Sat, 23 Jan 2016 02:03:40 +0000 (UTC)
From: "Arun Suresh (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12756768.1416510655000.187937.1453514620142@Atlassian.JIRA>
In-Reply-To: <JIRA.12756768.1416510655000@Atlassian.JIRA>
References: <JIRA.12756768.1416510655000@Atlassian.JIRA>
 <JIRA.12756768.1416510655637@arcas>
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


     [ 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.v7.patch

Thanks for the Review [~curino]. I've uploaded a new patch addressing some of your concerns..

# I like the idea of having specialized token for the new DistributedSchedulingProtocol. Ive raised YARN-4631 to track it
# I have removed the Assumption that resources are only mem and cpu and have updated {{DistSchedulerParams}} to reflect this.
# I understand *updateResourceAsk()* might seem confusing. I have changed the name and added some comments describing it.
# As for "resizing" the containers, yes, I wanted it to be consistent with the normalization that Fair/Capacity Scheduler performs to an ask. I have updated the patch to use the {{Resources.normalize()}} utility function.
# I have updated the patch with comments as why it needs to be a HashMap. Do let me know if it makes sense..

> 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-yarn-2877.v7.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)