[
https://issues.apache.org/jira/browse/YARN-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385522#comment-15385522
]
Hudson commented on YARN-5350:
------------------------------
ABORTED: Integrated in Hadoop-trunk-Commit #10122 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/10122/])
YARN-5350. Distributed Scheduling: Ensure sort order of allocatable (arun
suresh: rev 8fbe6ece24e38ee24fee0abdbed5f7dc5d3c16da)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/scheduler/LocalScheduler.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/scheduler/TestLocalScheduler.java
> 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
>
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
