hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (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 20:11:12 GMT

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

Arun Suresh commented on YARN-4412:
-----------------------------------

[~aw], I apologize..
But I did mentioned [here|https://issues.apache.org/jira/browse/YARN-4412?focusedCommentId=15148978&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15148978]
that the call to {{System.exit(-1)}} is actually intentional (the dispatch MUST bring down
the process if it hits a fatal error).. and was flagged as a consequence of (plain-vanilla
IDE assisted) refactoring of an existing inner class into a new class, which means its a findbugs
that already existed.

The patch process detects increase in findbugs due to a patch, but does not record a decrease,
which is the case with this patch..

Maybe there is a better alternative to using System.exit() ? But dont you feel that should
be explored outside of this JIRA ?

> 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