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

Sunil G commented on YARN-3733:
-------------------------------

In current patch, the new check for Float.isNaN() is done after the call to 
getResourceAsValue. Hence if clusterResource is 0 (for memory or for scores), 
there is a chance that we can get infinity.

So We may need option like 
* a) Verify infinity by calling *isInfinite(float v)*. Quoting from jdk7
{noformat}
isInfinite
public static boolean isInfinite(float v)
Returns true if the specified number is infinitely large in magnitude, false 
otherwise.
{noformat}
* b) Handle Exception for these cases. But not feeling a good options as we may 
lack backward compatibility.

>  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