[ https://issues.apache.org/jira/browse/YARN-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225522#comment-16225522 ]
Daniel Templeton commented on YARN-6953: ---------------------------------------- +1 from me as well, except that the patch doesn't appear to apply anymore. > 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 > 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 > > > 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: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org