[
https://issues.apache.org/jira/browse/YARN-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253981#comment-16253981
]
Hudson commented on YARN-6953:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13239 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13239/])
YARN-6953. Clean up (templedf: rev e094eb74b9e7d8c3c6f1990445d248b062cc230b)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/util/resource/ResourceUtils.java
> Clean up ResourceUtils.setMinimumAllocationForMandatoryResources() and
> setMaximumAllocationForMandatoryResources()
> ------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-6953
> URL: https://issues.apache.org/jira/browse/YARN-6953
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Affects Versions: YARN-3926
> Reporter: Daniel Templeton
> Assignee: Manikandan R
> Priority: Minor
> Labels: newbie
> Fix For: 3.1.0, 3.0.1
>
> Attachments: YARN-6953-YARN-3926-WIP.patch,
> YARN-6953-YARN-3926.001.patch, YARN-6953-YARN-3926.002.patch,
> YARN-6953-YARN-3926.003.patch, YARN-6953-YARN-3926.004.patch,
> YARN-6953-YARN-3926.005.patch, YARN-6953-YARN-3926.006.patch,
> YARN-6953.007.patch, YARN-6953.008.patch, YARN-6953.009.patch
>
>
> The {{setMinimumAllocationForMandatoryResources()}} and
> {{setMaximumAllocationForMandatoryResources()}} methods are quite convoluted.
> They'd be much simpler if they just handled CPU and memory manually instead
> of trying to be clever about doing it in a loop. There are also issues, such
> as the log warning always talking about memory or the last element of the
> inner array being a copy of the first element.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]