[
https://issues.apache.org/jira/browse/DRILL-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venki Korukanti reopened DRILL-2755:
------------------------------------
Initial patch \[1\] reports interrupts as failures in logs. This patch
addresses the issues to report interrupt to RpcOutcomeListener. Handle the
interrupt in RpcOutComeListener depending upon the implementation. Specific
details of the handling are here \[2\]
\[1\]
https://github.com/apache/drill/commit/3a294abcc51148e0e79096af5e6d3c45b7c19a9d
\[2\] Goto sheet "RpcOutcomeListener Impl" in
https://docs.google.com/spreadsheets/d/1phC5f7E6jn1WN-wXVdUllbIQ2k7K2ZftZzDdhDNLgtg/edit?usp=sharing
Review Board Link: https://reviews.apache.org/r/34120/
> 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
>
> Attachments:
> 0002-DRILL-2755-Use-and-handle-InterruptedException-durin.patch
>
>
> 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)
