Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 2 Jun 2014 08:34:02 +0000 (UTC)
From: "Wei Yan (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12707203.1396973975077.57080.1401698042581@arcas>
In-Reply-To: <JIRA.12707203.1396973975077@arcas>
References: <JIRA.12707203.1396973975077@arcas>
Subject: [jira] [Updated] (YARN-1913) With Fair Scheduler, cluster can
 logjam when all resources are consumed by AMs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wei Yan updated YARN-1913:
--------------------------

    Attachment: YARN-1913.patch

Thanks, Sandy.
Upload a new patch, move the AM resource usage check to AppSchedulable.

> With Fair Scheduler, cluster can logjam when all resources are consumed by AMs
> ------------------------------------------------------------------------------
>
>                 Key: YARN-1913
>                 URL: https://issues.apache.org/jira/browse/YARN-1913
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 2.3.0
>            Reporter: bc Wong
>            Assignee: Wei Yan
>         Attachments: YARN-1913.patch, YARN-1913.patch, YARN-1913.patch, YARN-1913.patch, YARN-1913.patch, YARN-1913.patch, YARN-1913.patch
>
>
> It's possible to deadlock a cluster by submitting many applications at once, and have all cluster resources taken up by AMs.
> One solution is for the scheduler to limit resources taken up by AMs, as a percentage of total cluster resources, via a "maxApplicationMasterShare" config.


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