[
https://issues.apache.org/jira/browse/YARN-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274425#comment-16274425
]
Jason Lowe commented on YARN-7541:
----------------------------------
Despite TestPBImplRecords being in the org.apache.hadoop.yarn.api package, it
is in the hadoop-yarn-common Maven project which this patch didn't touch. The
QA bot only runs tests in the projects touched by the patch. Looks like
TestPBImplRecords is testing some records which are not in the api project and
therefore can't be moved as-is there. Would be nice if this were split into
multiple tests, one per Maven project to tests the PBImpl classes in that
project.
> 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
> Fix For: 3.0.0, 3.1.0
>
> Attachments: YARN-7541.001.patch, YARN-7541.002.patch,
> YARN-7541.003.patch, YARN-7541.004.patch, YARN-7541.005.patch,
> YARN-7541.006.patch, YARN-7541.branch-3.0.001.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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
