[
https://issues.apache.org/jira/browse/TEZ-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14202447#comment-14202447
]
Siddharth Seth commented on TEZ-1742:
-------------------------------------
bq. Seems like we need a jira for the future to track how we can preempt a task
without killing the container?
Yep. There probably is a jira for this already, to handle interrupts correctly.
This also requires the processors to be written in a manner where they are
interruptable - which complicates things further.
> 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)
