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-4284) condition for AM blacklisting is too narrow
Date Fri, 23 Oct 2015 18:17:28 GMT

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

Jason Lowe commented on YARN-4284:
----------------------------------

Sorry for arriving a bit late.  I agree that DISKS_FAILED is too narrow of a failure to use
as a trigger, and it's probably better to err on the side of covering too many failure reasons
than not enough.

Patch looks pretty good, but I agree that we should not be blacklisting on preempted containers.
 Those have nothing to do with the AM or the node, and we shouldn't make the reschedule of
a preempted AM more difficult as a result.  There should be a test for that scenario.

> condition for AM blacklisting is too narrow
> -------------------------------------------
>
>                 Key: YARN-4284
>                 URL: https://issues.apache.org/jira/browse/YARN-4284
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.8.0
>            Reporter: Sangjin Lee
>            Assignee: Sangjin Lee
>         Attachments: YARN-4284.001.patch
>
>
> Per YARN-2005, there is now a way to blacklist nodes for AM purposes so the next app
attempt can be assigned to a different node.
> However, currently the condition under which the node gets blacklisted is limited to
{{DISKS_FAILED}}. There are a whole host of other issues that may cause the failure, for which
we want to locate the AM elsewhere; e.g. disks full, JVM crashes, memory issues, etc.
> Since the AM blacklisting is per-app, there is little practical downside in blacklisting
the nodes on *any failure* (although it might lead to blacklisting the node more aggressively
than necessary). I would propose locating the next app attempt to a different node on any
failure.



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

Mime
View raw message