[
https://issues.apache.org/jira/browse/YARN-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang updated YARN-5350:
------------------------------
Fix Version/s: (was: 3.0.0)
3.0.0-alpha1
> Distributed Scheduling: Ensure sort order of allocatable nodes returned by
> the RM is not lost
> ---------------------------------------------------------------------------------------------
>
> 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
> Fix For: 2.9.0, 3.0.0-alpha1
>
> Attachments: YARN-5350.001.patch, YARN-5350.002.patch,
> YARN-5350.003.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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
