[
https://issues.apache.org/jira/browse/YARN-7813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16355697#comment-16355697
]
Jason Lowe commented on YARN-7813:
----------------------------------
Thanks for the patch!
It looks like this has the potential to be surprising to users who had turned
on in-queue preemption. Previously the intra queue preemption selector was
keying off of cross-queue preemption disable, but now it will key off of a new
property. Will this cause queues to start performing intra-queue preemption
that did not previously with the same configs or vice-versa?
"intreQueuePreemptionDisabled" s/b "intraQueuePreemptionDisabled"
Why does CapacitySchedulerLeafQueueInfo have extra logic for getting
intra-queue preemption disabled status? I don't see this similar logic
elsewhere in the code.
Technically the queue CLI output changes are incompatible per
https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/Compatibility.html#Command_Line_Interface_.28CLI.29
> Capacity Scheduler Intra-queue Preemption should be configurable for each
> queue
> -------------------------------------------------------------------------------
>
> Key: YARN-7813
> URL: https://issues.apache.org/jira/browse/YARN-7813
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacity scheduler, scheduler preemption
> Affects Versions: 2.9.0, 2.8.3, 3.0.0
> Reporter: Eric Payne
> Assignee: Eric Payne
> Priority: Major
> Attachments: YARN-7813.001.patch
>
>
> Just as inter-queue (a.k.a. cross-queue) preemption is configurable per
> queue, intra-queue (a.k.a. in-queue) preemption should be configurable per
> queue. If a queue does not have a setting for intra-queue preemption, it
> should inherit its parents value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
