drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-4647) C++ client is not propagating a connection failed error when a drillbit goes down
Date Tue, 03 May 2016 15:34:13 GMT

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

ASF GitHub Bot commented on DRILL-4647:
---------------------------------------

GitHub user parthchandra opened a pull request:

    https://github.com/apache/drill/pull/493

    DRILL-4647: C++ client fails to propagate a dead connection error to …

    …the application.
    
    Return correct status from the DrillClient API if query submission fails.
    Also, propagate error back to the application thru the listener if query submission fails
or if there is a heartbeat failure before the response to query submission is received.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/parthchandra/drill DRILL-4647

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/drill/pull/493.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #493
    
----
commit e39f263eb18fb52d4105dfc8d3131357ca0a19a9
Author: Parth Chandra <parthc@apache.org>
Date:   2016-04-30T00:38:44Z

    DRILL-4647: C++ client fails to propagate a dead connection error to the application

----


> C++ client is not propagating a connection failed error when a drillbit goes down
> ---------------------------------------------------------------------------------
>
>                 Key: DRILL-4647
>                 URL: https://issues.apache.org/jira/browse/DRILL-4647
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Parth Chandra
>
> When a drillbit goes down, there are two conditions under which the client is not propagating
the error back to the application -
> 1) The application is in a submitQuery call: the ODBC driver is expecting that the error
be reported thru the query results listener which hasn't been registered at the point the
error is encountered.
> 2) A submitQuery call succeeded but never reached the drillbit because it was shutdown.
In this case the application has a handle to a query and is listening for results which will
never arrive. The heartbeat mechanism detects the failure, but is not propagating the error
to the query results listener.



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

Mime
View raw message