hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2293) Scoring for NMs to identify a better candidate to launch AMs
Date Tue, 15 Jul 2014 19:33:04 GMT

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

Jason Lowe commented on YARN-2293:
----------------------------------

This sounds very similar to YARN-2005, if a bit more general.  This approach sounds like it
could support a "gray" area for NMs where it really doesn't like to launch AMs on a node but
may choose to do so anyway if that's the only place it can find.  It may be more fruitful
to continue this discussion over on YARN-2005 and hash through how exit status would map to
scoring adjustments, how the score would affect scheduling, and work through various corner
cases.

> Scoring for NMs to identify a better candidate to launch AMs
> ------------------------------------------------------------
>
>                 Key: YARN-2293
>                 URL: https://issues.apache.org/jira/browse/YARN-2293
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager, resourcemanager
>            Reporter: Sunil G
>            Assignee: Sunil G
>
> Container exit status from NM is giving indications of reasons for its failure. Some
times, it may be because of container launching problems in NM. In a heterogeneous cluster,
some machines with weak hardware may cause more failures. It will be better not to launch
AMs there more often. Also I would like to clear that container failures because of buggy
job should not result in decreasing score. 
> As mentioned earlier, based on exit status if a scoring mechanism is added for NMs in
RM, then NMs with better scores can be given for launching AMs. Thoughts?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message