hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2187) FairScheduler: Disable max-AM-share check by default
Date Sat, 21 Jun 2014 07:27:24 GMT

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

Karthik Kambatla commented on YARN-2187:
----------------------------------------

+1. Committing this. 

> FairScheduler: Disable max-AM-share check by default
> ----------------------------------------------------
>
>                 Key: YARN-2187
>                 URL: https://issues.apache.org/jira/browse/YARN-2187
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: fairscheduler
>    Affects Versions: 2.5.0
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>         Attachments: YARN-2187.patch
>
>
> Say you have a small cluster with 8gb memory and 5 queues.  This means that equal queue
can have 8gb / 5 = 1.6gb but an AM requires 2gb to start so no AMs can be started.  By default,
max-am-share check should be disabled so users don't see a regression. On medium-sized clusters,
it still makes sense to set the max-am-share to a value between 0 and 1. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message