Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 15 Jun 2016 05:07:09 +0000 (UTC)
From: "Arun Suresh (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12979244.1465967196000.1079.1465967229531@Atlassian.JIRA>
In-Reply-To: <JIRA.12979244.1465967196000@Atlassian.JIRA>
References: <JIRA.12979244.1465967196000@Atlassian.JIRA> <JIRA.12979244.1465967196114@arcas>
Subject: [jira] [Created] (YARN-5255) Move ResourceRequest expansion for
 Delay Scheduling to the Scheduler
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 15 Jun 2016 05:07:16 -0000

Arun Suresh created YARN-5255:
---------------------------------

             Summary: Move ResourceRequest expansion for Delay Scheduling to the Scheduler
                 Key: YARN-5255
                 URL: https://issues.apache.org/jira/browse/YARN-5255
             Project: Hadoop YARN
          Issue Type: Bug
            Reporter: Arun Suresh


YARN-4879 proposes to enhance the Allocate Request by introducing a way to explicitly identify a ResourceRequest explicitly

Currently, if relaxLocality == true, a Node specific request is expanded to rack and *ANY* request by the {{AMRMClient}} before being sent to the Scheduler. The requires the 3 copies to perform locality specific delay scheduling.

It would be better to perform the expansion in the Scheduler itself, rather than the client, since:
# The expansion is not really specified in the ApplicationMasterProtocol, a non-java client will have to duplicate the expansion logic.
# Refactor out a lot of unnecessary code in the {{AMRMClientImpl}}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org