Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 8 May 2013 03:05:19 +0000 (UTC)
From: "Sandy Ryza (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12646551.1367982287634.285766.1367982319935@arcas>
In-Reply-To: <JIRA.12646551.1367982287634@arcas>
References: <JIRA.12646551.1367982287634@arcas>
Subject: [jira] [Created] (YARN-657) Fair scheduler can consider apps
 starved when they are alone on the cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Sandy Ryza created YARN-657:
-------------------------------

             Summary: Fair scheduler can consider apps starved when they are alone on the cluster
                 Key: YARN-657
                 URL: https://issues.apache.org/jira/browse/YARN-657
             Project: Hadoop YARN
          Issue Type: Bug
          Components: scheduler
    Affects Versions: 2.0.4-alpha
            Reporter: Sandy Ryza
            Assignee: Sandy Ryza


If a lone app on a cluster requests a lot of resources and it takes some time to allocate them, the fair scheduler may think the app is starved because it has not reached its minimum share.  This can cause confusing log messages and I believe unnecessary preemptions in certain edge cases where another app is running on the cluster but not using all the resources.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira