[
https://issues.apache.org/jira/browse/TEZ-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516988#comment-14516988
]
Rajesh Balamohan edited comment on TEZ-1752 at 4/28/15 1:01 PM:
----------------------------------------------------------------
- In case of AM sending shutdown signal, RuntimeTask.abort() is invoked so that
processors can get a chance for any cleanup.
- If the task is running, thread running the processor is interrupted
immediately; otherwise taskFuture.get() is interrupted.
- Adding the inputs/outputs as and when they are scheduled for initialization
in LogicalIOProcessorRuntimeTask
was (Author: rajesh.balamohan):
- If the task is running, thread running the processor is interrupted;
otherwise taskFuture.get() is interrupted.
- Adding the inputs/outputs as and when they are scheduled for initialization
in LogicalIOProcessorRuntimeTask
> Inputs / Outputs in the Runtime library should be interruptable
> ---------------------------------------------------------------
>
> Key: TEZ-1752
> URL: https://issues.apache.org/jira/browse/TEZ-1752
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Siddharth Seth
> Assignee: Rajesh Balamohan
> Attachments: TEZ-1752.1.patch, TEZ-1752.2.patch, TEZ-1752.3.patch,
> TEZ-1752.4.patch
>
>
> Not possible to preempt tasks without killing containers without this.
> There's still the problem of Processors not supporting interrupts. We may
> need API enhancements to either query IPOs on whether they are interrupbtible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
