hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4412) Create ClusterMonitor to compute ordered list of preferred NMs for OPPORTUNITIC containers
Date Mon, 16 May 2016 21:01:13 GMT

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

Vinod Kumar Vavilapalli commented on YARN-4412:
-----------------------------------------------

bq. 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.
Let's calm down. Don't ascribe laziness to situations that are better explained to be due
to ignorance.

[~asuresh], for intentional usages like this, there is a way to tell our findbugs infra to
ignore this so that our reports come clean. Look for findbugs-exclude.xml files in the code-base.

> 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


Mime
View raw message