[
https://issues.apache.org/jira/browse/YARN-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Payne updated YARN-6165:
-----------------------------
Attachment: YARN-6165.001.patch
{{IntraQueueCandidatesSelector#selectCandidates}} was not checking the
enable/disable status of each queue prior to calculating the
{{resToObtainByPartition}}.
To test this, I manually modified each of the tests in
{{TestProportionalCapacityPreemptionPolicyIntraQueue}} to disable preemption on
all of the test queues. Without this fix, the tests passed when they should
have failed. Meaning, with the preemption disabled on all of the test queues,
the tests continued to select containers for preemption. However, when I added
this fix, those modified tests started to fail.
[~sunilg], [~leftnoteasy], and [~jlowe], any comments would be greatly
appreciated.
> Intra-queue preemption occurs even when preemption is turned off for a
> specific queue.
> --------------------------------------------------------------------------------------
>
> Key: YARN-6165
> URL: https://issues.apache.org/jira/browse/YARN-6165
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler, scheduler preemption
> Affects Versions: 3.0.0-alpha2
> Reporter: Eric Payne
> Assignee: Eric Payne
> Attachments: YARN-6165.001.patch
>
>
> Intra-queue preemption occurs even when preemption is turned on for the whole
> cluster ({{yarn.resourcemanager.scheduler.monitor.enable == true}}) but
> turned off for a specific queue
> ({{yarn.scheduler.capacity.root.queue1.disable_preemption == true}}).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
