You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Chris Westin (JIRA)" <ji...@apache.org> on 2015/03/19 21:16:40 UTC

[jira] [Commented] (DRILL-2245) Improve Drillbit resiliency

    [ https://issues.apache.org/jira/browse/DRILL-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370030#comment-14370030 ] 

Chris Westin commented on DRILL-2245:
-------------------------------------

Review at https://reviews.apache.org/r/31435/

> Improve Drillbit resiliency
> ---------------------------
>
>                 Key: DRILL-2245
>                 URL: https://issues.apache.org/jira/browse/DRILL-2245
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Flow
>            Reporter: Chris Westin
>            Assignee: Chris Westin
>             Fix For: 0.8.0
>
>         Attachments: DRILL-2245.1.patch.txt, DRILL-2245.2.patch.txt, DRILL-2245.3-core.patch.txt, DRILL-2245.3-hygiene.patch.txt, DRILL-2245.4-core.patch.txt, DRILL-2245.5.patch.txt
>
>
> There are paths through WorkManager and Foreman that will allow a Drillbit to get wedged if there are failures. This can happen because events delivered via other threads will get stuck if Foreman throws an exception before it is accepting external events.
> This is a call to do some general cleanup here and make drillbits more robust so that they don't hang when there are query failures.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)