[ https://issues.apache.org/jira/browse/YARN-6057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801933#comment-15801933 ]
Daniel Templeton commented on YARN-6057: ---------------------------------------- In the case of both minimum and maximum, resource requests that are out of bounds are quietly adjusted to be in bounds. (See {{DefaultResourceCalculator.normalize()}} and {{DominantResourceCalculator.normalize()}}) The minimum will also prevent NMs that have fewer vcores from starting. (See {{ResourceTrackerService.registerNodeManager()}}.) > yarn.scheduler.minimum-allocation describtion update required > ------------------------------------------------------------- > > Key: YARN-6057 > URL: https://issues.apache.org/jira/browse/YARN-6057 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Bibin A Chundatt > Priority: Minor > > {code} > <property> > <description>The minimum allocation for every container request at the RM, > in terms of virtual CPU cores. Requests lower than this will throw a > InvalidResourceRequestException.</description> > <name>yarn.scheduler.minimum-allocation-vcores</name> > <value>1</value> > </property> > {code} > *Requests lower than this will throw a InvalidResourceRequestException.* > Only incase of maximum allocation vcore and memory > InvalidResourceRequestException is thrown -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org