[
https://issues.apache.org/jira/browse/TEZ-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14202415#comment-14202415
]
Siddharth Seth commented on TEZ-1742:
-------------------------------------
Also we should be careful about relying on pre-emption to achieve out of order
scheduling - since it effectively kills container re-use. Pre-emption should
ideally be the last resort in getting the correct tasks scheduled. IMHO, it's
best to trigger this only when attempts fail and need to be re-run, rather than
a mechanism to handle out of order scheduling.
> Improve response time of internal preemption
> --------------------------------------------
>
> Key: TEZ-1742
> URL: https://issues.apache.org/jira/browse/TEZ-1742
> Project: Apache Tez
> Issue Type: Task
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Fix For: 0.5.3
>
> Attachments: TEZ-1742.1.patch, TEZ-1742.2.patch, TEZ-1742.3.patch,
> TEZ-1742.4.patch
>
>
> Tez YARN Task Scheduler currently preempts 1 running task at a time when a
> higher priority task is waiting and there are no available resources. When a
> large number of higher priority tasks are pending then it can take a long
> time to preempt the required number of lower priority tasks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
