[
https://issues.apache.org/jira/browse/YARN-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093342#comment-15093342
]
Wangda Tan commented on YARN-4557:
----------------------------------
Thanks [~Naganarasimha],
Changes of PartitionedQueueComparator looks good, changes of
RegularContainerAllocator may be not correct:
Existing logic of non-exclusive partition allocation is:
- For a node heartbeat, try to run exclusive allocation allocation first
- If doesn't get any container allocated, try to run non-exclusive allocation
*for all apps/priorities".
If we allow allocate lower priority container first, priority inversion problem
could happen.
Thoughts?
> Few issues in scheduling with Node Labels
> -----------------------------------------
>
> Key: YARN-4557
> URL: https://issues.apache.org/jira/browse/YARN-4557
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Naganarasimha G R
> Assignee: Naganarasimha G R
> Priority: Minor
> Attachments: YARN-4557.v1.001.patch, YARN-4557.v2.001.patch,
> YARN-4557.v2.002.patch
>
>
> * When app has submitted requests for multiple priority in default partition,
> then if one of the priority requests has missed
> non-partitioned-resource-request equivalent to cluster size then container
> needs to be allocated. Currently if the higher priority requests doesn't
> satisfy the condition, then whole application is getting skipped instead the
> priority
> * When queue has * as accessibility, then the queue ordering was not
> happening properly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)