[
https://issues.apache.org/jira/browse/YARN-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466489#comment-15466489
]
Sunil G commented on YARN-4945:
-------------------------------
Thanks [~eepayne]
bq.LeafQueue#getApplications returns an umnodifiable Collection
Yes, I have made changes to handle this scenario.
bq.if it's already in selectedCandidates, it's because an inter-queue
preemption policy put it there
I think I must give some more clarity for what I am trying to do here. Its
possible that there can be some containers which were selected by
priority/user-limit policy may already be selected from inter-queue policies.
In that case, we need not have to mark them again. Rather we can deduct the
resource directly as its container marked for preemption.
bq.container's resources twice from toObtainByPartition
Its a mistake, I corrected the same in second patch.
> [Umbrella] Capacity Scheduler Preemption Within a queue
> -------------------------------------------------------
>
> Key: YARN-4945
> URL: https://issues.apache.org/jira/browse/YARN-4945
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Wangda Tan
> Attachments: Intra-Queue Preemption Use Cases.pdf,
> IntraQueuepreemption-CapacityScheduler (Design).pdf, YARN-2009-wip.2.patch,
> YARN-2009-wip.patch
>
>
> This is umbrella ticket to track efforts of preemption within a queue to
> support features like:
> YARN-2009. YARN-2113. YARN-4781.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
