You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Venki Korukanti (JIRA)" <ji...@apache.org> on 2015/05/04 20:31:07 UTC
[jira] [Commented] (DRILL-2755) Use and handle InterruptedException
during query processing
[ https://issues.apache.org/jira/browse/DRILL-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527009#comment-14527009 ]
Venki Korukanti commented on DRILL-2755:
----------------------------------------
https://docs.google.com/spreadsheets/d/1phC5f7E6jn1WN-wXVdUllbIQ2k7K2ZftZzDdhDNLgtg/edit?usp=sharing
Contains list of places where InterruptedException needs to handled and which threads to be interrupted when threads themselves are interrupted or when cancel request is received.
> Use and handle InterruptedException during query processing
> -----------------------------------------------------------
>
> Key: DRILL-2755
> URL: https://issues.apache.org/jira/browse/DRILL-2755
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
> Affects Versions: 0.8.0
> Reporter: Chris Westin
> Assignee: Venki Korukanti
> Fix For: 1.0.0
>
>
> Cancellation requests don't yet handle using InterruptedException to deal with blocking operations. For example, if a thread is blocked doing I/O, or waiting for completion of write requests (via SendingAccountor), then we need to be able to interrupt it so we can continue.
> This means both knowing what threads to interrupt, and for any relevant blocking sites to handle the InterruptedException correctly (see http://www.ibm.com/developerworks/library/j-jtp05236/). At present, most of these just log the exception and continue, effectively swallowing the exception, which is not correct.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)