Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Wed, 24 Dec 2014 00:16:13 +0000 (UTC)
From: "Parth Chandra (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12744799.1412027419000.94864.1419380173461@Atlassian.JIRA>
In-Reply-To: <JIRA.12744799.1412027419000@Atlassian.JIRA>
References: <JIRA.12744799.1412027419000@Atlassian.JIRA>
 <JIRA.12744799.1412027419693@arcas>
Subject: [jira] [Updated] (DRILL-1466) Drill Client receiving Handshake rpc
 calls from server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DRILL-1466?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Parth Chandra updated DRILL-1466:
---------------------------------
    Attachment:     (was: DRILL-1466.patch)

> Drill Client receiving Handshake rpc calls from server
> ------------------------------------------------------
>
>                 Key: DRILL-1466
>                 URL: https://issues.apache.org/jira/browse/DRILL-1466
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - C++
>            Reporter: Norris Lee
>            Assignee: Parth Chandra
>             Fix For: 0.8.0
>
>
> Occasionally in handleRead, the rpc type of the message coming back will =
be of type HANDSHAKE. Subsequent msgs coming back afterwards will be abnorm=
al/out of order.
> Case 1: the next call will be rpc type QUERY_RESULT where the query id is=
 0:0. QUERY_HANDLE was not called before this. This leads to the error ERR_=
QRY_OUTOFORDER with message: "Query result received before query id. Aborti=
ng =E2=80=A6"
> Case 2: the next call will be rpc type QUERY_HANDLE with coordination id =
0. This leads to error ERR_QRY_INVQUERYID with message "Cannot find query I=
d in internal structure"


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