Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 16 May 2016 19:50:13 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12917650.1449076669000.200243.1463428213122@Atlassian.JIRA>
In-Reply-To: <JIRA.12917650.1449076669000@Atlassian.JIRA>
References: <JIRA.12917650.1449076669000@Atlassian.JIRA> <JIRA.12917650.1449076669117@arcas>
Subject: [jira] [Commented] (YARN-4412) Create ClusterMonitor to compute
 ordered list of preferred NMs for OPPORTUNITIC containers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 16 May 2016 19:50:16 -0000


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

Allen Wittenauer commented on YARN-4412:
----------------------------------------

bq. The Findbugs will not be fixed.. as per this comment

WTF? Seriously? YARN-5075 has been opened to specifically deal with this issue since ya'll were too lazy to actually fix this correctly the first time. It's commits like this that cause the Apache Hadoop codebase quality to drop.

> Create ClusterMonitor to compute ordered list of preferred NMs for OPPORTUNITIC containers
> ------------------------------------------------------------------------------------------
>
>                 Key: YARN-4412
>                 URL: https://issues.apache.org/jira/browse/YARN-4412
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager, resourcemanager
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>             Fix For: 3.0.0-alpha1
>
>         Attachments: YARN-4412-yarn-2877.v1.patch, YARN-4412-yarn-2877.v2.patch, YARN-4412-yarn-2877.v3.patch, YARN-4412-yarn-2877.v4.patch, YARN-4412-yarn-2877.v5.patch, YARN-4412-yarn-2877.v6.patch, YARN-4412.007.patch, YARN-4412.008.patch, YARN-4412.009.patch
>
>
> Introduce a Cluster Monitor that aggregates load information from individual Node Managers and computes an ordered list of preferred Node managers to be used as target Nodes for OPPORTUNISTIC container allocations. 
> This list can be pushed out to the Node Manager (specifically the AMRMProxy running on the Node) via the Allocate Response. This will be used to make local Scheduling decisions


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org