You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Arun Suresh (JIRA)" <ji...@apache.org> on 2016/07/11 00:40:10 UTC

[jira] [Updated] (YARN-5350) Ensure LocalScheduler does not lose the sort order of allocatable nodes returned by the RM

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

Arun Suresh updated YARN-5350:
------------------------------
    Attachment: YARN-5350.001.patch

Attaching trivial patch.
Most of the code changes are in refactoring the testcase. [~subru], can you give it a quick rev ?

> 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
>         Attachments: YARN-5350.001.patch
>
>
> 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