[
https://issues.apache.org/jira/browse/YARN-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903699#comment-13903699
]
Junping Du commented on YARN-1724:
----------------------------------
I would prefer more to remove sort rather than adding a lock. No matter sort or
not, it will iterate all nodes and see if can do attemptScheduling() which make
sort sounds unnecessary. It only make sense when we skip some nodes with less
resources but additional lock may be needed. Thoughts?
> Race condition in Fair Scheduler when continuous scheduling is turned on
> -------------------------------------------------------------------------
>
> Key: YARN-1724
> URL: https://issues.apache.org/jira/browse/YARN-1724
> Project: Hadoop YARN
> Issue Type: Bug
> Components: scheduler
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: YARN-1724-1.patch, YARN-1724.patch
>
>
> If nodes resource allocations change during
> Collections.sort(nodeIdList, nodeAvailableResourceComparator);
> we'll hit:
> java.lang.IllegalArgumentException: Comparison method violates its general
> contract!
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
