[ https://issues.apache.org/jira/browse/YARN-8808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631359#comment-16631359 ]
Arun Suresh commented on YARN-8808: ----------------------------------- bq. containersUtilization and nodeUtilization in SchedulerNode are always instantiated (to ResourceUtilization.newInstance(0, 0, 0f)), so getNodeUtilization() / getAggregatedContainersUtilization() should never return null, unless I am missing somthing Again, I noticed the NPE in a testcase setup and I had to put the check. It is possible it might not happen in a real cluster. > Use aggregate container utilization instead of node utilization to determine > resources available for oversubscription > --------------------------------------------------------------------------------------------------------------------- > > Key: YARN-8808 > URL: https://issues.apache.org/jira/browse/YARN-8808 > Project: Hadoop YARN > Issue Type: Sub-task > Affects Versions: YARN-1011 > Reporter: Haibo Chen > Assignee: Haibo Chen > Priority: Major > Attachments: YARN-8088-YARN-1011.01.patch, > YARN-8808-YARN-1011.00.patch > > > Resource oversubscription should be bound to the amount of the resources that > can be allocated to containers, hence the allocation threshold should be with > respect to aggregate container utilization. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org