You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Mehant Baid (JIRA)" <ji...@apache.org> on 2014/11/12 01:38:35 UTC

[jira] [Resolved] (DRILL-1592) Detect drillbit failure and cancel running queries.

     [ https://issues.apache.org/jira/browse/DRILL-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mehant Baid resolved DRILL-1592.
--------------------------------
    Resolution: Fixed

Resolved in c305c794a21d8d657897cbbf85c66fc0d1adc024

> Detect drillbit failure and cancel running queries. 
> ----------------------------------------------------
>
>                 Key: DRILL-1592
>                 URL: https://issues.apache.org/jira/browse/DRILL-1592
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Jinfeng Ni
>            Assignee: Jinfeng Ni
>         Attachments: 0002-DRILL-1592-Detect-drillbit-failure-and-cancel-the-af.patch
>
>
> When Drillbit dies or was killed,  the running queries might be hang there, and the sqlline would also hang there. There are two cases:
> 1. The Drillbit having the foreman dies, or the foreman thread dies, but the rest of non-root fragments are still running, even though the connection between the client and the foreman has been lost.
> 2. The Drillbit running the non-root fragments dies, but foreman and other non-root fragments are still running.
> In either cases, Drill should have a way to detect such node failure, and cancel the running queries, and return to a state where client could submit a new query, or re-connect (if connection is lost in case foreman dies) to a different foreman.



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