hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3733) DominantRC#compare() does not work as expected if cluster resource is empty
Date Tue, 02 Jun 2015 10:08:18 GMT

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

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

Hi [~rohithsharma]
Thanks for the detailed scenario.

Scenario 4 can be possible, correct?. clusterResource<0,0> : lhs <2,2> and rhs
<3,2>.

Currently getResourceAsValue gives back the max ratio of mem/vcores if dominent. Else gives
the min ratio.
If clusterResource is 0, then could we directly send the max of mem/vcore if dominent, and
min in other case. This has to be made more better algorithm when more resources comes in.
This is not completely perfect as we treat memory and vcores leniently. Pls share your thoughts.

> DominantRC#compare() does not work as expected if cluster resource is empty
> ---------------------------------------------------------------------------
>
>                 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: 0001-YARN-3733.patch, 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)

Mime
View raw message