hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yufei Gu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7541) Node updates don't update the maximum cluster capability for resources other than CPU and memory
Date Sat, 25 Nov 2017 08:11:00 GMT

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

Yufei Gu commented on YARN-7541:
--------------------------------

Jenkins failed https://builds.apache.org/job/PreCommit-YARN-Build/18660/console

> Node updates don't update the maximum cluster capability for resources other than CPU
and memory
> ------------------------------------------------------------------------------------------------
>
>                 Key: YARN-7541
>                 URL: https://issues.apache.org/jira/browse/YARN-7541
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>    Affects Versions: 3.0.0-beta1, 3.1.0
>            Reporter: Daniel Templeton
>            Assignee: Daniel Templeton
>            Priority: Critical
>         Attachments: YARN-7541.001.patch, YARN-7541.002.patch, YARN-7541.003.patch, YARN-7541.004.patch,
YARN-7541.005.patch
>
>
> When I submit an MR job that asks for too much memory or CPU for the map or reduce, the
AM will fail because it recognizes that the request is too large.  With any other resources,
however, the resource requests will instead be made and remain pending forever.  Looks like
we forgot to update the code that tracks the maximum container allocation in {{ClusterNodeTracker}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
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