[ 
https://issues.apache.org/jira/browse/YARN-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567184#comment-14567184
 ] 

Rohith commented on YARN-3733:
------------------------------

Thanks [~devaraj.k] and [~sunilg] for review

bq. Can we check for lhs/rhs emptiness and compare these before ending up with 
infinite values? 
If we calculater for emptyness, this would affect specific input values like 
clusterResource=<0,0> lhs=<1,1>, and rhs<2,2>. Then which one is considered as 
dominant? bcs directly dominant component can not be retrieved by memory or cpu.

And I listed out what are the possible combination of inputs would ocure in 
YARN. These are
||Sl.no||clusterResorce||lhs||rhs||Remark||
|1|<0,0>|<0,0>|<0,0>|Valid Input;Handled|
|2|<0,0>|<positive integer,positive integer>|<0,0>|NaN vs Infinity: Patch 
Handle This scenario|
|3|<0,0>|<0,0>|<positive integer,positive integer>|Nan vs Infinity: Patch 
Handle This scenario|
|4|<0,0>|<positive integer,positive integer>|<positive integer,positive 
integer>|Infinity vs Infinity: Can this type can ocur in YARN?|
|5|<0,0>|<positive integer,0>|<0,positive integer>|Is this valid input? Can 
this type can ocur in YARN?|


>  On RM restart AM getting more than maximum possible memory when many  tasks 
> in queue
> -------------------------------------------------------------------------------------
>
>                 Key: YARN-3733
>                 URL: https://issues.apache.org/jira/browse/YARN-3733
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.7.0
>         Environment: Suse 11 Sp3 , 2 NM , 2 RM
> one NM - 3 GB 6 v core
>            Reporter: Bibin A Chundatt
>            Assignee: Rohith
>            Priority: Blocker
>         Attachments: YARN-3733.patch
>
>
> Steps to reproduce
> =================
> 1. Install HA with 2 RM 2 NM (3072 MB * 2 total cluster)
> 2. Configure map and reduce size to 512 MB  after changing scheduler minimum 
> size to 512 MB
> 3. Configure capacity scheduler and AM limit to .5 
> (DominantResourceCalculator is configured)
> 4. Submit 30 concurrent task 
> 5. Switch RM
> Actual
> =====
> For 12 Jobs AM gets allocated and all 12 starts running
> No other Yarn child is initiated , *all 12 Jobs in Running state for ever*
> Expected
> =======
> Only 6 should be running at a time since max AM allocated is .5 (3072 MB)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to