Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 11 Jul 2016 00:39:11 +0000 (UTC)
From: "Arun Suresh (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12988163.1468197496000.72856.1468197551013@Atlassian.JIRA>
In-Reply-To: <JIRA.12988163.1468197496000@Atlassian.JIRA>
References: <JIRA.12988163.1468197496000@Atlassian.JIRA> <JIRA.12988163.1468197496670@arcas>
Subject: [jira] [Created] (YARN-5350) Ensure LocalScheduler does not lose
 the sort order of allocatable nodes returned by the RM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 11 Jul 2016 00:39:12 -0000

Arun Suresh created YARN-5350:
---------------------------------

             Summary: Ensure LocalScheduler does not lose the sort order of allocatable nodes returned by the RM
                 Key: YARN-5350
                 URL: https://issues.apache.org/jira/browse/YARN-5350
             Project: Hadoop YARN
          Issue Type: Sub-task
            Reporter: Arun Suresh
            Assignee: Arun Suresh


The LocalScheduler receives an ordered list of nodes from the RM with each allocate call. This list, which is used by the LocalScheduler to allocate OPPORTUNISTIC containers, is sorted on the Nodes free capacity (queue length / wait time).

Unfortunately, the LocalScheduler stores this list in a HashMap thereby losing the sort order.

The trivial fix would be to replace the HashMap with a LinkedHashMap which retains the insertion order.


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

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