[ https://issues.apache.org/jira/browse/YARN-9509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193082#comment-17193082 ]
Hadoop QA commented on YARN-9509: --------------------------------- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s{color} | {color:blue} Docker mode activated. {color} | | {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 5s{color} | {color:red} https://github.com/apache/hadoop/pull/766 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} | \\ \\ || Subsystem || Report/Notes || | GITHUB PR | https://github.com/apache/hadoop/pull/766 | | JIRA Issue | YARN-9509 | | Console output | https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-766/1/console | | versions | git=2.17.1 | | Powered by | Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org | This message was automatically generated. > Capped cpu usage with cgroup strict-resource-usage based on a mulitplier > ------------------------------------------------------------------------ > > Key: YARN-9509 > URL: https://issues.apache.org/jira/browse/YARN-9509 > Project: Hadoop YARN > Issue Type: New Feature > Components: nodemanager > Reporter: Nicolas Fraison > Priority: Minor > > Add a multiplier configuration on strict resource usage to authorize > container to use spare cpu up to a limit. > Currently with strict resource usage you can't get more than what you request > which is sometime not good for jobs that doesn't have a constant usage of cpu > (for ex. spark jobs with multiple stages). > But without strict resource usage we have seen some bad behaviour from our > users that don't tune at all their needs and it leads to some containers > requesting 2 vcore but constantly using 20. > The idea here is to still authorize containers to get more cpu than what they > request if some are free but also to avoid too big differencies so SLA on > jobs is not breached if the cluster is full (at least increase of runtime is > contain) -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org